You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The requirement originates from a use case to make variable substitution in custom fields.
For example, to substitute namespace in ambassador configuration which is stored in metadata/annotations/getambassador.io\/config, we need to make changes as below:
create var in kustomization.yaml
add field spec to kustomizeconfig.yaml and included it
It ends up in lots of code fragment when you have to handle lots of different fields and make it hard to refactoring the overlays (you shall have to cut and paste the code fragment from one overlay to another).
It would be nice to declare such changes close to where it is used, e.g. the annotation of related resource.
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
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
k8s-ci-robot
added
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Aug 2, 2019
The requirement originates from a use case to make variable substitution in custom fields.
For example, to substitute namespace in ambassador configuration which is stored in
metadata/annotations/getambassador.io\/config
, we need to make changes as below:kustomization.yaml
kustomizeconfig.yaml
and included itIt ends up in lots of code fragment when you have to handle lots of different fields and make it hard to refactoring the overlays (you shall have to cut and paste the code fragment from one overlay to another).
It would be nice to declare such changes close to where it is used, e.g. the annotation of related resource.
For example, given the manifest below.
The content of annotation
sigs.k8s.io/kustomize/mixin
shall be parsed and mixed intokustomization.yaml
on the fly.The text was updated successfully, but these errors were encountered: