doc: Add design doc for blb migration #8034
Conversation
k8s-ci-robot
added
release-note-none
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nilo19 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
approved
✅ Deploy Preview for kubernetes-sigs-cloud-provide-azure ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
|
||
| > The following `User` stands for human users, or any cluster provisioning tools (e.g., AKS). | ||
|
|
||
| 1. User must manually decouples all virtual machines from the Basic Load Balancer backend pool before migration. |
There was a problem hiding this comment.
could we do this in our codes? it should be possible as we already have the cleanup logic (need some changes to preserve IP)
There was a problem hiding this comment.
Sure, as we can have the service object so we know the ip information, no need to have another way to preserve IP.
|
|
||
| 2. User must change the Load Balancer sku in the configuration file from `Basic` to `Standard`. | ||
|
|
||
| 3. If the basic Load Balancer is not removed, it will be deleted during the migration. |
There was a problem hiding this comment.
if SLB outbound is required, then basic LB must be deleted and recreate with same name
|
|
||
| ## Design | ||
|
|
||
| > The following `User` stands for human users, or any cluster provisioning tools (e.g., AKS). |
There was a problem hiding this comment.
If SLB outbound not needed, could we migrate just after user change sku to standard and restart ccm?
What type of PR is this?
/kind documentation
What this PR does / why we need it:
doc: Add design doc for blb migration
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: