influxdata / influxdata/helm-charts
InfluxDB-CLustered3 - licenses.influxdata.io CRD requires kubit-applier service account to have clusterrole and clusterrolebinding
- Dominant language
- Mustache
- Stars
- 257
- Forks
- 347
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 9
Description
When reconciling the AppInstance, the kubit-applier service account needs the following RBAC to manage the CRD licenses.influxdata.io:
`
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: kubeit-applier
rules:
- apiGroups:
- apiextensions.k8s.io
resources:
- customresourcedefinitions
verbs:
- create
- delete
- get
- list
- patch
- update
- watch
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: kubit-applier
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: kubit-applier
subjects:
- kind: ServiceAccount
name: kubeit-applier
namespace: influxdb
`
Contributor guide
Research direction
Start by locating the InfluxDB-Clustered3 Helm chart templates that define the kubit-applier service account and RBAC. Compare the rendered resources with the ClusterRole and ClusterRoleBinding shown in the issue, then render the chart to verify the service account can manage licenses.influxdata.io custom resource definitions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, yaml
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100