appmesh-prometheus chart deployment fails on EKS with Kubernetes Version 1.22
- Dominant language
- Mustache
- Stars
- 1.3k
- Forks
- 1.1k
- Avg merge
- 22m
- Merged PRs (30d)
- 5
Description
**Describe the bug**
appmesh-prometheus chart deployment fails on EKS with Kubernetes Version 1.22
**Steps to reproduce**
```
admin1:~/environment $ kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.0", GitCommit:"c2b5237ccd9c0f1d600d3072634ca66cefdf272f", GitTreeState:"clean", BuildDate:"2021-08-04T18:03:20Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22+", GitVersion:"v1.22.6-eks-7d68063", GitCommit:"f24e667e49fb137336f7b064dba897beed639bad", GitTreeState:"clean", BuildDate:"2022-02-23T19:29:12Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}
admin1:~/environment $ kubectl get ns appmesh-system
NAME STATUS AGE
appmesh-system Active 49d
admin1:~/environment $ helm upgrade -i appmesh-prometheus eks/appmesh-prometheus --namespace appmesh-system
Release "appmesh-prometheus" does not exist. Installing it now.
Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "ClusterRole" in version "rbac.authorization.k8s.io/v1beta1", unable to recognize "": no matches for kind "ClusterRoleBinding" in version "rbac.authorization.k8s.io/v1beta1"]
```
**Expected outcome**
appmesh-prometheus chart is deployed successfully on EKS with Kubernetes Version 1.22
**Environment**
* Chart name: appmesh-prometheus
* Chart version: 1.0.0
* Kubernetes version: 1.22
* Using EKS (yes/no), if so version? yes, eks.1
**Additional Context**:
```
admin1:~/environment $ helm search repo appmesh-prometheus
NAME CHART VERSION APP VERSION DESCRIPTION
eks/appmesh-prometheus 1.0.0 2.13.1 App Mesh Prometheus Helm chart for Kubernetes
```
Contributor guide
Research direction
Start by inspecting the appmesh-prometheus chart version 1.0.0 and its rendered RBAC manifests. Reproduce the Helm installation on Kubernetes 1.22/EKS and check the rbac.authorization.k8s.io/v1beta1 ClusterRole and ClusterRoleBinding errors; done means the chart deploys successfully with the reported environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100