Introduce the ability to deploy Kube app using Kustomize

[joshua-portainer]

We are looking for feedback around introducing the ability to deploy a kube app using Kustomize.

This would be made accessible on the advanced deployment page when selecting Git repository

This would allow Administrators and standard users to create an application.

EE-2173

[joshua-portainer]

This is a mockup for reference purposes only and the resulting feature may look different.

[author: Joshua Cassin, created at: 2021-12-17T09:58:53.934+1300]
[created from EE-2173, comment 15819]

[DerStoffel]

Hey @joshua-portainer,

while you are looking for feedback, I'd highly welcome that introduction.
Also not just the format, but having it connected would be amazing.

Cheers

[joshua-portainer]

Thanks @DerStoffel,

You mentioned having it connected, Are you able to elaborate further on how you see that working?

[DerStoffel]

Hi @joshua-portainer,

a lot of secrets and/or configs are often put in place during runtime through environment variables.
That makes maintenance of compose files and similar a bit tedious through multiple variants, and maybe having to put things in you don't want to have versioned anyway.

Right now portainer has the doubtful practice of basically copying compose-files or similar into it without the capability of updating it. That leads to either using ci to update automatically or building something around it.

I would like to maintain configs in Kustomize and on change I want portainer to update, with the help of portainer. So portainer listening for changes.

Does that help?

[hookenz]

H @stevensbkang @Anthony-Portainer +100 to this. It's a huge gaping hole omission to Kubernetes. Please consider adding it soon.

Basically you want to check into git

base/
|--- deployment.yaml
...
overlays/dev
|--- kustomization.yaml
  ...
overlays/prod
|--- kustomization.yaml
   ...

And have Portainer deploy a customisation based on dev or prod or whatever you define.
Without it you have to jump through some custom external hoops and check in the output and then have portainer work from that resulting output. It makes things just that bit harder.

Outside of portainer:

kubectl kustomize  ./overlays/prod > output.yaml

Then check in output.yaml somewhere and use portainer gitops from there.

Seems a bit counter intuitive.