Generator Annotations

[sethpollack]

When should I use:

internal.config.kubernetes.io/generatorBehavior: merge
internal.config.kubernetes.io/needsHashSuffix: enabled

vs

kustomize.config.k8s.io/behavior: merge
kustomize.config.k8s.io/needs-hash: "true"

[k8s-ci-robot]

@sethpollack: This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[KnVerey]

Annotations with the "internal" prefix are details of the current implementation of Kustomize and should not be used directly. The only exception is a couple specific annotations that are part of the KRM Function specification and can be referenced by function authors (but still should never be added or seen by end users).

Out of curiosity, where did you find references to those annotations?

/kind support

[sethpollack]

I'm using this in my KRM plugin and its adding those annotations.

	return p.h.ResmapFactory().FromSecretArgs(
		kv.NewLoader(p.h.Loader(), p.h.Validator()), p.SecretArgs)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale