How to create K8s objects like PriorityClass alongside charts?

[daaain]

We're using the "official" gcloud-sqlproxy chart, but node upgrades right now are quite painful as other charts get scheduled before the proxy and start throwing errors due to the missing database connection.

After doing a bit of reading it sounds like setting pod priority using a PriorityClass and the priorityClassName annotation could solve the issue, but after doing a fair bit of reserach I couldn't find any obvious way to create the PriorityClass Kubernetes object alongside the proxy chart.

Is there a way to make this use case work in particular or Kubernetes objects created outside of charts in general?

Now thinking of it, is the solution to set up a chart for these global objects? If so, is there a way to guarantee that chart would be created before other charts to ensure the K8s object exists?

[mumoshu]

@daaain Hey!

incubator/raw chart can be used to turn a set of k8s resource definitions into a helm chart. For more information, I'd suggest reading #494 (comment).

You can use sub-helmfiles(helmfiles: in your helmfile.yaml) for ordering. #137 would help getting more context on this. Let me also add that there's no guaranteed ordering in releases: though, as one of helmfile's ability is parallelize those by setting --concurrency=N.

[mumoshu]

#649 would allow you to add any K8s resources into your helm release, without modifying or forking the chart at all. I hope either that or the standard usage og incubator/chart solves your issue 😃

[daaain]

Thanks a lot for your replies @mumoshu, really appreciated!

I have been working on other priorities (pun not intended 😹) so couldn't try the approaches you suggested, but I must say I particularly like the idea of helm-x integration as it would make the chart extension the most obvious! I'll report back once I got a solution working.

As an aside weaveworks/flagger referenced in #649 looks really useful too!