Jx: Add support for kustomize

[jstrachan]

it would be awesome to be able to use kustomize YAML in an environment git repository to provide environment specific overrides for apps.

e.g. having a folder structure...

kustomize/
  app1/
    mydeployment.yaml
  app2/
    someservice.yaml

Then when using no tiller we use helm to generate the YAML and post process it. We could trivially detect the kustomize folder and then just run kustomize against the YAML before we apply it - i.e. here: https://github.com/jenkins-x/jx/blob/master/pkg/helm/helm_template.go#L284

we'd just need to

(i) add kustomise to our builder images
(ii) detect the kustomize folder in the current folder and apply it before the above line.

simples!

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[fentas]

/remove-lifecycle stale

[jstrachan]

we may also want to support kustomise folder in the preview chart in an app if we want to do any customisation to the preview chart charts/preview/kustomize/*.yaml e.g. to kustomize a dependent chart (postgres or something)

[polothy]

is there a way to support these things with helm3? no tiller has its own drawbacks* and we were hoping helm3 would solve all our problems ;) (I know... it'll make new ones!)

* Doesn't support deploying to multiple namespaces, misses deleting resources like custom CRDS, etc.

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.