Investigate using Kustomize 2.x

[justaugustus]

There are some breaking changes from kustomize 1.x --> 2.x that would prevent us from simply bumping the version.

ref:

• https://github.com/kubernetes-sigs/kustomize/blob/master/docs/version2.0.0.md
• clean up bazel workspace dependencies #126 (comment)
• Kustomize 2.0+ not compatible with getting started guide cluster-api-provider-aws#569
• Kustomize should use bases instead of resources cluster-api-provider-aws#611

/kind feature
/priority important-longterm
/milestone baseline
/help

[k8s-ci-robot]

@justaugustus:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

There are some breaking changes from kustomize 1.x --> 2.x that would prevent us from simply bumping the version.

ref:

• https://github.com/kubernetes-sigs/kustomize/blob/master/docs/version2.0.0.md
• clean up bazel workspace dependencies #126 (comment)
• Kustomize 2.0+ not compatible with getting started guide cluster-api-provider-aws#569
• Kustomize should use bases instead of resources cluster-api-provider-aws#611

/kind feature
/priority important-longterm
/milestone baseline
/help

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.

[serbrech]

related : kubernetes-sigs/kubebuilder#614
Kubebuilder updated their scaffolding to match Kustomize v2 expectations.

[serbrech]

Instructions to fix structure :
kubernetes-sigs/kubebuilder#595 (comment)

[serbrech]

/assign @serbrech

[k8s-ci-robot]

@serbrech: GitHub didn't allow me to assign the following users: serbrech.

Note that only kubernetes-sigs members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign serbrech

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.

[serbrech]

Further investigations :
the secretGenerator type has done away with commands: for security concerns.
it has has now plugins, which allow you to define where the secrets are pulled from.
Environment is one option that is easy to swap in.
see : kubernetes-sigs/kustomize#760

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

[justaugustus]

No longer required as we've moved to kustomize 3.x in v1alpha2.