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.

Sign up for GitHub

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

Jump to bottom

Document how to upgrade from v1alpha2 to v1alpha3 #1550

Closed
vincepri opened this issue Oct 15, 2019 · 5 comments · Fixed by #2520
Closed

Document how to upgrade from v1alpha2 to v1alpha3 #1550

vincepri opened this issue Oct 15, 2019 · 5 comments · Fixed by #2520
Assignees
@noamran
Labels
kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v0.3.0

Comments

@vincepri
Copy link
Member

This is a release blocker, we need documentation on how to upgrade from v1alpha2 providers to v1alpha3.

/kind documentation
@vincepri vincepri added this to the v0.3.0 milestone Oct 15, 2019
@k8s-ci-robot k8s-ci-robot added the kind/documentation Categorizes issue or PR as related to documentation. label Oct 15, 2019
@vincepri vincepri mentioned this issue Oct 15, 2019
Merged
@detiber
Copy link
Member

detiber commented Oct 15, 2019

@vincepri can you please add some more context on the CABPK related changes for v1alpha2 to v1alpha3? especially around the way the components will no longer be distributed from the old repo and the manager will no longer be a separate Deployment?

@vincepri
Copy link
Member Author

Yeah, once I get more items, I'll open the sub-issues, this is to track the larger effort of upgrading from v1alpha2

@ncdc ncdc added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Dec 6, 2019
@noamran
Copy link
Contributor

noamran commented Jan 22, 2020

/assign

@ncdc ncdc mentioned this issue Feb 6, 2020
Closed
@rudoi
Copy link
Contributor

rudoi commented Feb 7, 2020

Just to document a few things I've run into slapping v1alpha3 onto v1alpha2:

The ClusterRoleBinding "capi-manager-rolebinding" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"ClusterRole", Name:"capi-aggregated-manager-role"}: cannot change roleRef

The Deployment "capi-controller-manager" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"cluster.x-k8s.io/provider":"cluster-api", "control-plane":"cluster-api-controller-manager"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable

@vincepri
Copy link
Member Author

vincepri commented Mar 2, 2020

@noamran any updates on this? is there anything we can help with?

@noamran noamran mentioned this issue Mar 4, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@noamran noamran

Labels
kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v0.3.0
Development

Successfully merging a pull request may close this issue.

📖 Upgrade v1alpha2 to v1alpha3 documentation noamran/cluster-api
6 participants
@ncdc @detiber @vincepri @rudoi @k8s-ci-robot @noamran