Charts: [incubator/fluentd-cloudwatch] extensions/v1beta1 support

[pfraedrichmss]

incubator/fluentd-cloudwatch relies on kind DaemonSet being part of the extensions/v1beta1; this support was removed in Kubernetes 1.16.

Version of Helm and Kubernetes:
Helm: version.BuildInfo{Version:"v3.1.2", GitCommit:"d878d4d45863e42fd5cff6743294a11d28a9abce", GitTreeState:"clean", GoVersion:"go1.13.8"}

Kube: 1.17.4

Which chart:
incubator/fluentd-cloudwatch

What happened:
Install fails with message
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "DaemonSet" in version "extensions/v1beta1"

What you expected to happen:
Chart to be installed

How to reproduce it (as minimally and precisely as possible):
Install incubator/fluentd-cloudwatch on Kubernetes 1.16+

Anything else we need to know:
Reference: https://github.com/kubernetes/kubernetes/issues/84782

[noguilty4you]

I have the same issue trying to install the gitlab.com's "Elastic Stack" K8S addon.

K8S: DigitalOcean Managed, version 1.16.6-do.2

"install-elastic-stack" container log:
`+ helm init --upgrade
Creating /root/.helm
Creating /root/.helm/repository
Creating /root/.helm/repository/cache
Creating /root/.helm/repository/local
Creating /root/.helm/plugins
Creating /root/.helm/starters
Creating /root/.helm/cache/archive
Creating /root/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Adding local repo with URL: http://127.0.0.1:8879/charts
$HELM_HOME has been configured at /root/.helm.

Tiller (the Helm server-side component) has been updated to gcr.io/kubernetes-helm/tiller:v2.16.3 .

• seq 1 30
• helm version --tls --tls-ca-cert /data/helm/elastic-stack/config/ca.pem --tls-cert /data/helm/elastic-stack/config/cert.pem --tls-key /data/helm/elastic-stack/config/key.pem
  Client: &version.Version{SemVer:"v2.16.3", GitCommit:"1ee0254c86d4ed6887327dabed7aa7da29d7eb0d", GitTreeState:"clean"}
  Server: &version.Version{SemVer:"v2.16.3", GitCommit:"1ee0254c86d4ed6887327dabed7aa7da29d7eb0d", GitTreeState:"clean"}
• s=0
• break
• exit 0
• helm repo update
  Hang tight while we grab the latest from your chart repositories...
  ...Skip local chart repository
  ...Successfully got an update from the "stable" chart repository
  Update Complete.
• helm upgrade elastic-stack stable/elastic-stack --install --atomic --cleanup-on-fail --reset-values --tls --tls-ca-cert /data/helm/elastic-stack/config/ca.pem --tls-cert /data/helm/elastic-stack/config/cert.pem --tls-key /data/helm/elastic-stack/config/key.pem --version 1.9.0 --set 'rbac.create=true,rbac.enabled=true' --namespace gitlab-managed-apps -f /data/helm/elastic-stack/config/values.yaml
  Release "elastic-stack" does not exist. Installing it now.
  INSTALL FAILED
  PURGING CHART
  Error: validation failed: unable to recognize "": no matches for kind "DaemonSet" in version "apps/v1beta2"
  Error: release: "elastic-stack" not found
  `

[benjamink]

DaemonSet is no longer available in the extensions/v1beta1 branch - you need to switch to using apps/v1 since Kubernetes 1.16: https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/

[stale[bot]]

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.

[pfraedrichmss]

This is still a breaking issue on Kube 1.16 -- someone from the Helm team please chime in here.

Ignoring submitted issues is not a great way to instill confidence in your user community.

[larsderidder]

Also running into this issue. The solution seems easy as @benjamink said. Not sure about a workaround though.

[stale[bot]]

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.

[pfraedrichmss]

More than two months and still no reply or even acknowledgement from the
repo maintainers. Unacceptable. I will keep this issue alive and open until
it’s fixed.

[stale[bot]]

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.

[pfraedrichmss]

Three months and counting...

[stale[bot]]

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.

[peterfraedrich]

Four months and counting...

[davidegiunchi]

@peterfraedrich one of the latest release does solve this problem. I'm using the helm chart of fluentd-cloudwatch on EKS 1.17

[peterfraedrich]

@davidegiunchi thanks for the heads up.

How is it acceptable in this community that the maintainers never even:

• Updated the issue to state that this fix was being included in the latest release
• Updated the issue to state that the fix has been completed and is in the latest release
• Closed out the issue when the latest release was released

Instead they:

• Ignored the issue
• Never once even commented to say it was being worked on
• Never even assigned it to someone to investigate

@lachie83 @prydonius @sameersbn @viglesiasce @unguiculus @scottrigby @mattfarina @davidkarlsen @paulczar @cpanato @jlegrone @maorfr

[stale[bot]]

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.

[peterfraedrich]

Five month bump.

[stale[bot]]

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.

[peterfraedrich]

6 month bump

[stale[bot]]

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.

[pfraedrichmss]

7 month bump

On Fri, Dec 25, 2020 at 9:10 AM stale[bot] [e-mail] wrote:

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.

—

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/helm/charts/issues/21662#issuecomment-751254834, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AOBX77BOUCEH7W4WCVKKY63SWSMM5ANCNFSM4LVIA2KA
.

>

PETER FRAEDRICH
CTO & Co-Founder

M: 703-819-9704
E: [email protected]