Hey everyone! I'm exploring a declarative and GitOps-friendly approach to manage Kubernetes PriorityClass resources. I'm considering creating a dedicated Helm chart just for our PriorityClass definitions and using a HelmRelease custom resource with something like Flux CD to deploy it. This would help me centralize management, keep everything version-controlled in Git, and make updates or rollbacks easier. Is this a recommended practice in a GitOps setup? Are there any potential issues or best practices I should keep in mind? I'd love to see any relevant examples as well. Thanks for your input!
3 Answers
Honestly, creating a Helm chart just to do this seems a bit much. Think about how many priority classes you'll have and how often they change. If it's just a handful, keeping it simple with plain YAML would serve you better.
You might want to stick with a plain YAML file for this. It does the job for managing PriorityClasses just fine, and with Flux, you can pull directly from Git without the need for a Helm chart. We have a few single manifests like that, and it works great! If you prefer a Helm chart, it's okay too, just not really necessary for such a simple case.
Using raw charts is a solid choice for situations like this. I get why you'd consider Helm, but make sure you actually need the added complexity. If your classes won't change much, you might not need a full chart. Terraform is also a great tool for managing Kubernetes resources; might be worth checking out!
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures