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.

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

Review the upgrade guides R5->R6 and Migration to KaaS v2 and update if necessary #744

Open
matofeder opened this issue Jul 5, 2024 · 1 comment · May be fixed by #745 or #746
Open

Review the upgrade guides R5->R6 and Migration to KaaS v2 and update if necessary #744

matofeder opened this issue Jul 5, 2024 · 1 comment · May be fixed by #745 or #746
Assignees
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling
Milestone

Comments

@matofeder
Copy link
Member

As a KaaS administrator, I want smooth KaaS upgrades based on the docs guides.

Consider the latest CAPO API changes and whether they could affect our upgrade guides in docs.

@matofeder matofeder added the Container Issues or pull requests relevant for Team 2: Container Infra and Tooling label Jul 5, 2024
@matofeder matofeder changed the title Review the upgrade guide R5->R6and update if necessery Review the upgrade guides R5->R6and Migration to KaaS v2 and update if necessery Jul 5, 2024
@Nils98Ar
Copy link
Member

Nils98Ar commented Jul 5, 2024

Feedback:

  • The first option here (with the fixed versions) should be used everywhere
  • This part seems (partly) redundant with this part
  • Add a hint here and here how to do the update of the files manually, especially cluster-template.yaml. We diffed our customized R5-cluster-template.yaml with the original R5-cluster-template.yaml and applied the diff to the new R6-cluster-template.yaml.
  • The maintained/7.* branches mentioned in the upgrade guide are not available.
  • Maybe add support for CAPO API v1beta1? Or in the next release...
  • Here the OPENSTACK_CLUSTER_GEN needs to be incremented as well. Otherwise the create_cluster.sh had problems with immutable specs values in our case.
  • The check if the cluster-template.yaml has already been updated could be improved. In our case the grep found occurrences of provider-id already before the update (probably we used the main branch in an older state) but the rest was not there. Maybe it would be good to replace the or with and and in the grep?

@chess-knight chess-knight changed the title Review the upgrade guides R5->R6and Migration to KaaS v2 and update if necessery Review the upgrade guides R5->R6 and Migration to KaaS v2 and update if necessary Aug 1, 2024
@chess-knight chess-knight moved this from Backlog to Todo in Sovereign Cloud Stack Aug 7, 2024
@chess-knight chess-knight linked a pull request Aug 7, 2024 that will close this issue
@chess-knight chess-knight added this to the R7 (v8.0.0) milestone Aug 8, 2024
@chess-knight chess-knight moved this from Todo to Doing in Sovereign Cloud Stack Aug 16, 2024
@chess-knight chess-knight linked a pull request Aug 23, 2024 that will close this issue
This was linked to pull requests Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling
Projects
Status: In Review
3 participants