-
Notifications
You must be signed in to change notification settings - Fork 45
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
Downgrade from dev/2.5 to dev/2.4 does not work #2058
Labels
Milestone
Comments
TeddyAndrieux
added a commit
that referenced
this issue
Nov 20, 2019
Currently downgrade do not working because we downgrade all kubernetes objects before downgrading the API server of the bootstrap node and kubernetes 1.16 removed the support of DaemonSet and other objects using `extensions/v1beta1`, since we use `extensions/v1beta1` to deploy coredns in dev/2.4 we cannot downgrade it. Sees: #2058
TeddyAndrieux
added a commit
that referenced
this issue
Nov 20, 2019
Currently downgrade do not working because we downgrade all kubernetes objects before downgrading the API server of the bootstrap node and kubernetes 1.16 removed the support of DaemonSet and other objects using `extensions/v1beta1`, since we use `extensions/v1beta1` to deploy coredns in dev/2.4 we cannot downgrade it. Sees: #2058
gdemonet
pushed a commit
that referenced
this issue
Nov 21, 2019
Currently downgrade does not work because we downgrade all Kubernetes objects before downgrading the API server of the bootstrap node. Kubernetes 1.16 removed the support of some APIs that we use in the 2.4 branch, hence we cannot downgrade without re-ordering the whole process. See: #2058
maybe related to #2081 ? |
Fixed by #2101 |
ChengYanJin
pushed a commit
that referenced
this issue
Dec 17, 2019
Currently downgrade does not work because we downgrade all Kubernetes objects before downgrading the API server of the bootstrap node. Kubernetes 1.16 removed the support of some APIs that we use in the 2.4 branch, hence we cannot downgrade without re-ordering the whole process. See: #2058
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component:
'salt', 'kubernetes'
What happened:
In dev/2.4 we use
extensions/v1beta1
API do deploy kube-proxy DaemonSet but this API get removed in k8s 1.16 (which is the version we use in dev/2.5) so when we try to downgrade kube-proxy and our APIserver still using dev/2.5 version (k8s 1.16)extensions/v1beta1
do not existsThis
extensions/v1beta1
is already deprecated in dev/2.4 and should not have been used (since metalk8s-2.4.0 and metalk8s-2.4.1 are released with this API this issue need to be handle in downgrade process of dev/2.5)What was expected:
Working downgrade from dev/2.5 to dev/2.4
Steps to reproduce
Try to downgrade from dev/2.5 to dev/2.4
Resolution proposal (optional):
TBD:
2 proposition:
apps/v1
instead ofextensions/v1beta1
to "downgrade" DaemonSet + no longer use depreacted API in any metalk8s branchsThe text was updated successfully, but these errors were encountered: