Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

[stable/couchdb] StatefulSet won't deploy on k8s 1.16 #17680

Closed
jjvilleg opened this issue Oct 3, 2019 · 2 comments
Closed

[stable/couchdb] StatefulSet won't deploy on k8s 1.16 #17680

jjvilleg opened this issue Oct 3, 2019 · 2 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@jjvilleg
Copy link

jjvilleg commented Oct 3, 2019

Describe the bug
CouchDB StatefulSet cannot be deployed on k8s 1.16 because of deprecated API use.

Version of Helm and Kubernetes:
1.16 K8s
Helm Version doesn't matter

Which chart:
incubator/couchdb
stable/couchdb

What happened:
When you try to deploy the chart on k8s 1.16, you get an error
Error: validation failed: unable to recognize "": no matches for kind "StatefulSet" in version "apps/v1beta2"

What you expected to happen:
It should deploy successfully.

How to reproduce it (as minimally and precisely as possible):
Try deploying the chart on k8s 1.16.
Minikube 1.4.0 can be used to reproduce this issue.

Anything else we need to know:
https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/

@stale
Copy link

stale bot commented Nov 2, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 2, 2019
@jjvilleg
Copy link
Author

jjvilleg commented Nov 4, 2019

Moved and closed with apache/couchdb-helm#2

@jjvilleg jjvilleg closed this as completed Nov 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant