-
Notifications
You must be signed in to change notification settings - Fork 8
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.
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
docs: Added guide to migrate to Ubuntu 24.04 #409
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice and clear steps 👍
migration/ubuntu/20-to-24.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please rename this file to 20.04-to-22.04-openstack.md
to make it clearer that it is only for openstack.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that was an error on my part of course it should be 20.04-to-24.04-openstack.md
😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea, I should've seen that as well 🙈
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. Minor thing: the document is named 20.04-to-22.04
, but it should be 20.04-to-24.04
, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you update these ones as well?
- Update DNS records to point to the new control plane nodes | ||
|
||
> [!NOTE] | ||
> This is only needed if you are using DNS and are pointing that to the IPs of the control plane nodes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> This is only needed if you are using DNS and are pointing that to the IPs of the control plane nodes. | |
> Updating the DNS records is only needed if you are using DNS and are pointing that to the IPs of the control plane nodes. |
- Update loadbalancer to use the endpoints of the new control plane nodes | ||
|
||
> [!NOTE] | ||
> This is only needed if you are using a loadbalancer in front of the API server. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> This is only needed if you are using a loadbalancer in front of the API server. | |
> Updating the loadbalancer is only needed if you are using a loadbalancer in front of the API server. |
``` | ||
|
||
> [!NOTE] | ||
> This will likely fail at some point in one or two ways: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> This will likely fail at some point in one or two ways: | |
> Removing the old control plane nodes will likely fail at some point in one or two ways: |
- Remove the old control plane floating IPs from group vars under the key `supplementary_addresses_in_ssl_keys` | ||
|
||
> [!NOTE] | ||
> This is not needed if you are using a loadbalancer in front of the API server. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> This is not needed if you are using a loadbalancer in front of the API server. | |
> Removing the old IPs from `supplementary_addresses_in_ssl_keys` is not needed if you are using a loadbalancer in front of the API server. |
I thought I searched for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice that we can now do this migration!
Warning
This is a public repository, ensure not to disclose:
What kind of PR is this?
Required: Mark one of the following that is applicable:
Optional: Mark one or more of the following that are applicable:
Important
Breaking changes should be marked
kind/admin-change
orkind/dev-change
depending on typeCritical security fixes should be marked with
kind/security
What does this PR do / why do we need this PR?
Migration docs for how to migrate to ubuntu 24.04
Information to reviewers
Checklist
NetworkPolicy Dashboard