We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
操作步骤: 1、在ks中已创建了一个配置了lb的服务,lb的配置为service.beta.kubernetes.io/qingcloud-load-balancer-eip-source: auto
2、待成功创建lb并绑定了lb后,修改该服务的lb配置方式为如下: service.beta.kubernetes.io/qingcloud-load-balancer-eip-strategy为reuse-lb, 设置service.beta.kubernetes.io/qingcloud-load-balancer-id为已存在的其他的lb
3、待修改生效后,查看步骤1中服务绑定的lb下面的监听器及后端
预期结果: 修改服务的lb配置后,会解绑之前绑定的lb
实际结果: 修改服务的lb配置后,未解绑之前绑定的lb,该服务同时被绑定了2个lb
The text was updated successfully, but these errors were encountered:
No branches or pull requests
操作步骤:
1、在ks中已创建了一个配置了lb的服务,lb的配置为service.beta.kubernetes.io/qingcloud-load-balancer-eip-source: auto
2、待成功创建lb并绑定了lb后,修改该服务的lb配置方式为如下:
service.beta.kubernetes.io/qingcloud-load-balancer-eip-strategy为reuse-lb,
设置service.beta.kubernetes.io/qingcloud-load-balancer-id为已存在的其他的lb
3、待修改生效后,查看步骤1中服务绑定的lb下面的监听器及后端
预期结果:
修改服务的lb配置后,会解绑之前绑定的lb
实际结果:
修改服务的lb配置后,未解绑之前绑定的lb,该服务同时被绑定了2个lb
The text was updated successfully, but these errors were encountered: