-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Filebeat Helm deployment reports use of deprected k8s api #1055
Comments
Hi @rpastrana, |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi @jmlrt, is Elastic planing on supporting K8s v1.17+ ? If so, it seems this issue needs to be addressed. Thanks. |
@rpastrana, |
@jmlrt great to hear! Will that change be tracked by this ticket? |
Yes it is. We have really low bandwith currently so unfortunately I don't expect it to be worked soon but we have some time until 1.22. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Commenting in hopes this does comes out of triage/stale |
Hi @rpastrana, I took a bit more time to investigate this, and I don't find any place where From what I see, everything was already done in #890. Can you give a bit more details about what is still missing? |
The ingress object still uses networking.k8s.io/v1beta1 See other defects (duplicate?) #1444 |
Hi,
My suspicion is that the reference to "rbac.authorization.k8s.io/v1beta1" is still included in the included template file ...
Helm chart version 7.16.1 Helm version 3.7.2 Minikube version: 1.24.0 kubectl version
workaround: |
@codebue this seems to be the case because the reference to kube-state-metrics is quite old. They changed the ClusterRole API with this commit: prometheus-community/helm-charts@0e9f68e But this is the version 2.9.3 metricbeat is using 2.4.1 in the requirements file. |
Closing this issue as it was created for Filebeat. |
* feat: bumping kube-state-metrics to version 4.2.0 - #1055 Signed-off-by: Jan Ole Rundshagen <[email protected]> * update doc and tests to use prometheus-community helm repo * bump kube-state-metric version Co-authored-by: jmlrt <[email protected]>
* feat: bumping kube-state-metrics to version 4.2.0 - elastic#1055 Signed-off-by: Jan Ole Rundshagen <[email protected]> * update doc and tests to use prometheus-community helm repo * bump kube-state-metric version Co-authored-by: jmlrt <[email protected]>
* feat: bumping kube-state-metrics to version 4.2.0 - #1055 Signed-off-by: Jan Ole Rundshagen <[email protected]> * update doc and tests to use prometheus-community helm repo * bump kube-state-metric version Co-authored-by: jmlrt <[email protected]> Co-authored-by: Jan Rundshagen <[email protected]>
Chart version:
7.9.3
Kubernetes version:
v3.5.0
Kubernetes provider: E.g. GKE (Google Kubernetes Engine)
Minikube
Helm Version:
v3.5.0
helm get release
outpute.g.
helm get elasticsearch
(replaceelasticsearch
with the name of your helm release)Be careful to obfuscate every secrets (credentials, token, public IP, ...) that could be visible in the output before copy-pasting.
If you find some secrets in plain text in
helm get release
output you should use Kubernetes Secrets to managed them is a secure way (see Security Example).Output of helm get release
Helm based deployment of Filebeat, and ES produce the following warnings:
W0128 13:25:59.736302 3118 warnings.go:70] rbac.authorization.k8s.io/v1beta1 ClusterRole is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRole
W0128 13:25:59.738266 3118 warnings.go:70] rbac.authorization.k8s.io/v1beta1 ClusterRoleBinding is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRoleBinding
W0128 13:25:59.832285 3118 warnings.go:70] rbac.authorization.k8s.io/v1beta1 ClusterRole is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRole
W0128 13:25:59.837044 3118 warnings.go:70] rbac.authorization.k8s.io/v1beta1 ClusterRoleBinding is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRoleBinding
Steps to reproduce:
W0128 13:25:59.736302 3118 warnings.go:70] rbac.authorization.k8s.io/v1beta1 ClusterRole is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRole
W0128 13:25:59.738266 3118 warnings.go:70] rbac.authorization.k8s.io/v1beta1 ClusterRoleBinding is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRoleBinding
W0128 13:25:59.832285 3118 warnings.go:70] rbac.authorization.k8s.io/v1beta1 ClusterRole is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRole
W0128 13:25:59.837044 3118 warnings.go:70] rbac.authorization.k8s.io/v1beta1 ClusterRoleBinding is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRoleBinding
Expected behavior:
No ClusterRole, ClusterRoleBinding warnings
Provide logs and/or server output (if relevant):
See above
Be careful to obfuscate every secrets (credentials, token, public IP, ...) that could be visible in the output before copy-pasting
Asked questions here, but received no traction: https://discuss.elastic.co/t/filebeat-helm-deployment-reports-use-of-deprected-k8s-api/262671
The text was updated successfully, but these errors were encountered: