[X] I've searched for similar issues and couldn't find anything matching
[X] I've discussed this feature request in the K8sGPT Slack and got positive feedback
Is this feature request related to a problem?
None
Problem Description
When we switched from having the operator's code, creating all k8sgpt rbac permissions for good reasons and put them in helm chart's manifests, we effectively lost the ability to provision a functional k8sgpt pod whilst running the operator in local mode due to the fact the permissions are coming from the helm chart which is not part of operator's local development.
Solution Description
I think there are many ways to solve this issue and I don't have strong opinions.
The result will be the creation of RBAC permissions along with the service account during operator's local development workflow.
An approach will be to update the way make install is used right now to include the helm chart RBAC manifests
Benefits
Parity between operator's helm chart templates and local development's manifests
Potential Drawbacks
No response
Additional Information
Preferably we need to have a better way to use kubebuilder's Makefile (kustomize) and our own helm chart templates' development in parity during operator's development
Checklist
Is this feature request related to a problem?
None
Problem Description
When we switched from having the operator's code, creating all k8sgpt rbac permissions for good reasons and put them in helm chart's manifests, we effectively lost the ability to provision a functional k8sgpt pod whilst running the operator in local mode due to the fact the permissions are coming from the helm chart which is not part of operator's local development.
Solution Description
I think there are many ways to solve this issue and I don't have strong opinions. The result will be the creation of RBAC permissions along with the service account during operator's local development workflow.
An approach will be to update the way
make installis used right now to include the helm chart RBAC manifestsBenefits
Parity between operator's helm chart templates and local development's manifests
Potential Drawbacks
No response
Additional Information
Preferably we need to have a better way to use kubebuilder's Makefile (kustomize) and our own helm chart templates' development in parity during operator's development