hack: Test hybrid cluster upgrades#18246
Conversation
Workers with a fixed list of API server IPs in BootConfig don't need protokube to populate /etc/hosts. Use that signal directly instead of gating on cluster-wide gossip mode.
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/test pull-kops-aws-upgrade-k135-ko135-to-k136-kolatest-many-addons |
|
/test pull-kops-aws-upgrade-k134-ko134-to-k136-kolatest-many-addons |
|
/test pull-kops-aws-upgrade-k135-ko135-to-k136-kolatest-many-addons |
Add UseLoadBalancerForKopsController. When it returns true, expose kops-controller on the API NLB and bake the LB IPs into worker BootConfig.APIServerIPs so workers bootstrap without protokube. Control-plane nodes keep gossip.
Add the kops-controller forwarding rule and ingress firewall rule for gossip clusters with an internal API load balancer.
Advertise control-plane port IPs as KubeAPIServer endpoints so workers seed /etc/hosts with control-plane addresses and reach kops-controller on port 3988 directly. Existing firewall rules already permit the worker to control-plane path.
Expose kops-controller on the cluster load balancer for gossip Azure clusters with an API LB. Drop the unused UsesPrivateDNS clause. Signed-off-by: Ciprian Hacman <ciprian@hakman.dev>
Signed-off-by: Ciprian Hacman <ciprian@hakman.dev>
d2261f9 to
0d3d3db
Compare
|
/test pull-kops-aws-upgrade-k135-ko135-to-k136-kolatest-many-addons |
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/cc @rifelpet