Filebeat Helm deployment reports use of deprected k8s api

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

How critical are this warnings in k8s api v 1.17 - v 1.21 and should Filebeat update the templates in order to support k8s api v1.122+ ?

Deploying Elastic Stack as 3rd party dependency in my Helm chart.yaml as such:
dependencies:

  • name: filebeat # Managed stderr log-forwarder
    version: 7.9.3
    repository: https://helm.elastic.co
    condition: elasticsearch.enabled
  • name: elasticsearch # Managed logging processor engine
    version: 7.9.3
    repository: https://helm.elastic.co
    condition: elasticsearch.enabled
  • name: kibana # Optional managed logging processor front-end
    version: 7.9.3
    repository: https://helm.elastic.co
    condition: kibana.enabled #should only enable if elasticsearch.enabled=true

helm version
version.BuildInfo{Version:"v3.5.0", GitCommit:"32c22239423b3b4ba6706d450bd044baffdcf9e6", GitTreeState:"clean", GoVersion:"go1.15.6"}

Kubernetes
v1.19.3

Hi @Rodrigo_LN,
Thanks for reporting this, this will be tracked in Filebeat Helm deployment reports use of deprected k8s api · Issue #1055 · elastic/helm-charts · GitHub.