search

kubernetes-sigs / kustomize

Customization of kubernetes YAML configurations
Apache License 2.0
10.91k stars 2.24k forks source link

build command to result in output configurations within appropriate nested directories structure if need be. #2254

Closed govinda-attal closed 4 years ago

govinda-attal commented 4 years ago

We are planning to use kpt functions and kustomize along with each other.

Kpt functions when apply config changes and later if output is sink to a target directory, it can generate the output files in relevant directories. I think it is able to do so with help of these annotations: (please note config.kubernetes.io/path)

annotations: config.kubernetes.io/index: '0' config.kubernetes.io/path: 'ocp/kustomization.yaml'

It could be really handy of kustomize to keep track of file paths and help in generating output suitably.

We plan to use these (kpt and kustomize) for Anthos config-connector resources, which requires to have configs in a repo in this structure: https://cloud.google.com/anthos-config-management/docs/concepts/repo?hl=sl.

Any thoughts or direction could help.

pwittrock commented 4 years ago

@govinda-attal This is something we plan to tackle by rebasing kustomize on top of the same libraries used by kpt functions -- the kyaml libraries in the kustomize repo. Will also address a number of other issues such as keeping comments and structure.

pwittrock commented 4 years ago

@monopole another rebase issue

fejta-bot commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/kustomize/issues/2254#issuecomment-668306140): >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](https://github.com/fejta). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.