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

[BUG] Kubernetes v1.16 incompatibility #213

Closed
palexster opened this issue Sep 20, 2019 · 4 comments
Closed

[BUG] Kubernetes v1.16 incompatibility #213

palexster opened this issue Sep 20, 2019 · 4 comments
Labels
bug Something isn't working component/k8s

Comments

@palexster
Copy link
Collaborator

palexster commented Sep 20, 2019

Describe the bug

As found by Aldo, Kubernetes v1.16 dropped the legacy support for:
apiVersion extensions/v1beta1
in favor of:
apiVersion: apps/v1

This breaks the Polycube CNI installation, resulting in a kubernetes failure, as the current plugin declares the compatibility with the old API and cannot be installed in K8s 1.16 and onwards.

To Reproduce

Trying to apply polycube CNI manifest, we get:


error: unable to recognize "https://raw.githubusercontent.com/polycube-network/polycube/master/src/components/k8s/standalone_etcd.yaml": no matches for kind "Deployment" in version "extensions/v1beta1"

Additional context

The apiVersion change is documented here: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/

@palexster palexster added bug Something isn't working component/k8s labels Sep 20, 2019
@palexster palexster changed the title [BUG] Kubernetes v1.16 [BUG] Kubernetes v1.16 incompatibility Sep 20, 2019
@asimpleidea
Copy link
Contributor

I have grep-ed all the files that contain the unsupported apiVersion and replaced with the new one.
I'll make a PR when I have finished building the docker and tested it with k8s 1.16.

@alacuku
Copy link
Contributor

alacuku commented Sep 20, 2019

I already have a working version of the three configuration files: pcn-k8s.yaml, standalone_etcd.yaml and echoserver_nodeport.yaml. Should I make a pull request or we wait for the Elis' fix?

@frisso
Copy link
Contributor

frisso commented Sep 20, 2019

Is Elis fix ok? If so, we can simply accept his fix and merge.

@frisso
Copy link
Contributor

frisso commented Sep 20, 2019

Closed with #214

@frisso frisso closed this as completed Sep 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working component/k8s
Projects
None yet
Development

No branches or pull requests

4 participants