Labels support for Transformer Configurations about kustomize HOT 8 CLOSED

Highly interested as well!

from kustomize.

/kind support
/triage needs-information

from kustomize.

Hi @stormqueen1990 👋

I tested your suggestion and it indeed works - I guess I should have rtfm!

Our GitOps pipeline uses a common set of configs that are referenced when applications are promoted between environments. Having transformer configuration support for labels would help ease the transition from commonLabels (and let us utilize the sweet new functionality to ignore selectors 😀).

While a desirable feature, I understand if it is something that cannot be implemented. We can certainly make things work using labels.fields.

Thanks!

Edit: It currently is not in the manual. Thank you for creating an issue to add it.

from kustomize.

Hi @stormqueen1990 👋

I tested your suggestion and it indeed works - I guess I should have rtfm!

Our GitOps pipeline uses a common set of configs that are referenced when applications are promoted between environments. Having transformer configuration support for labels would help ease the transition from commonLabels (and let us utilize the sweet new functionality to ignore selectors 😀).

While a desirable feature, I understand if it is something that cannot be implemented. We can certainly make things work using labels.fields.

Thanks!

Edit: It currently is not in the manual. Thank you for creating an issue to add it.

Nice to know this addresses your use case! I added a note to record this feedback in #5436 (comment), as the deprecation of commonLabels is being handled through that other issue.

I will be closing this issue but feel free to reopen if needed!

/close

from kustomize.

/assign @stormqueen1990

from kustomize.

Hello there, @ciaccotaco! 👋

The labels structure in the Kustomization file can optionally take a list of fields to which you would like to apply the labels. I tested it locally and it appears to cover the use case you described in this issue, but would you please give it a try and confirm whether it works for your use case?

The configuration I tested looks similar to the following:

labels:
  - includeSelectors: false # or true
    includeTemplates: true  # or false
    pairs:
      app: myapp
      contact: username
      department: kustomize
      environment: dv
    fields:
      - path: spec/podTemplate/metadata/labels
        create: true
        kind: FlinkDeployment
      - path: spec/jobManager/podTemplate/metadata/labels
        create: true
        kind: FlinkDeployment
      - path: spec/taskManager/podTemplate/metadata/labels
        create: true
        kind: FlinkDeployment

resources:
  - resources/flinkdeployment.yaml

Note the absence of the configurations section in this example.

from kustomize.

/remove-kind feature

from kustomize.

@stormqueen1990: Closing this issue.

from kustomize.