Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[feature]bcs-k8s-watch跨云环境下对于health可配置化支持 #18

Closed
bryanhe-bupt opened this issue May 8, 2019 · 0 comments
Closed

[feature]bcs-k8s-watch跨云环境下对于health可配置化支持 #18

bryanhe-bupt opened this issue May 8, 2019 · 0 comments
Assignees
@bryanhe-bupt
Labels
confirmed issue is confirmed feature new feature inner issue comes from Tencent side
Milestone
1.15.x功能迭代

Comments

@bryanhe-bupt
Copy link
Contributor

feature相关背景与描述
跨云环境下，bcs-k8s-watch通过zk获取的bcs-health的地址是无法直接访问的，需要通过代理才能访问。

解决方案描述
在bcs-k8s-watch的启动配置中，指定bcs-health的地址。当启动配置中指定了bcs-health的地址时，直接使用该地址，不再通过zk获取bcs-health地址。
@bryanhe-bupt bryanhe-bupt added the feature new feature label May 8, 2019
@bryanhe-bupt bryanhe-bupt added this to the 1.13.x功能迭代 milestone May 8, 2019
@bryanhe-bupt bryanhe-bupt self-assigned this May 8, 2019
@DeveloperJim DeveloperJim added confirmed issue is confirmed inner issue comes from Tencent side labels May 10, 2019
@DeveloperJim DeveloperJim changed the title [feature] [feature]bcs-k8s-watch跨云环境下对于health可配置化支持 May 10, 2019
DeveloperJim pushed a commit that referenced this issue Dec 4, 2020
@AlexAi27
Merge pull request #18 from Tencent/master
eaddec0 
Merge from main repository
ifooth pushed a commit to ifooth/bk-bcs that referenced this issue Apr 10, 2024
@AlkaidChan
feat: add metrics (TencentBlueKing#18)
9864c86 
* feat: add metrics

* feat: add metrics

* feat: add metrics
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bryanhe-bupt bryanhe-bupt

Labels
confirmed issue is confirmed feature new feature inner issue comes from Tencent side
Projects
None yet
Milestone
1.15.x功能迭代
Development

No branches or pull requests
2 participants
@DeveloperJim @bryanhe-bupt