Investigate how to keep helm chart in sync with deploy manifest

[leakingtapan]

Is your feature request related to a problem? Please describe.
We created Helm chart for the driver here. Since we still have a deploy/kubernetes/manifest.yaml, this creates a problem about how to sync the two.

Describe the solution you'd like in detail
Potential solutions:

• deprecate the deploy/kubernetes/manifest.yaml (not ideal)
• Evaluate Kustomize
• etc.

Additional Context

• We have aws-alb-ingress-controler that is doing the same thing, I will check on that side how is this problem solved there.

[fejta-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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[leakingtapan]

/remove-lifecycle stale

[fejta-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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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 kubernetes/test-infra repository.

[krmichel]

/reopen

[k8s-ci-robot]

@krmichel: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

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 kubernetes/test-infra repository.

[krmichel]

@leakingtapan, I don't know if this has been dealt with, but I think that if helm template was used with a correct values file it could be used to create the base manifests. Then the helm chart could be maintained and Kustomize manifests could just synced by generating them from the chart. Thoughts?

[leakingtapan]

/reopen
It’s a good idea :) would you be interested in helping on this?

[k8s-ci-robot]

@leakingtapan: Reopened this issue.

In response to this:

/reopen
It’s a good idea :)

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 kubernetes/test-infra repository.

[krmichel]

/remove-lifecycle rotten
Yeah, let me read up a little bit more on Kustomize and I will take a crack at it.