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

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

/remove-lifecycle stale

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

@KnVerey I read in the docs that both the Go and the Exec plugins are slated for deprecation .. May I undertsand a rough timeline / target release for the removal of those from Kustomize? ..

We do know that we will remove them eventually, but there's no specific target yet. It will depend in part on when we're able to fully activate the replacements in kubectl kustomize (which only releases 3x/year), as we'll need an overlap release before removal. (Re "Exec" deprecation: In case it isn't clear, the KRM Functions version of Exec extensions is being preserved/graduated.)

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

/remove-lifecycle stale

Hey there! I'm learning how Kustomize works (and also plugins). I still don't understand what KRM-driven feature means; however, I'm actively reading and I included some notes about my study and todos for later. These are personal todos that I'm planning to come back to but I think they might help others.

Jargon note: For an explanation about the Kubernetes Resource Model (KRM) term, see the following links.

1. https://github.com/kubernetes/design-proposals-archive/blob/main/architecture/resource-management.md
2. https://twitter.com/bgrant0607/status/1406998402768859137?lang=en
3. https://github.com/kubernetes-sigs/kustomize/blob/master/cmd/config/docs/api-conventions/functions-spec.md
4. https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/2953-kustomize-plugin-graduation#key-terminology

And also see the example in the Kubernetes Resource Model (KRM) Functions Specification Examples section. I can't parse the example yet; however, it seems to allude to containers that take input and print output so I'm guessing the example might work in a Unix pipeline like the following command illustrates.

$ echo hello | docker run --interactive debian bash -c 'cat; echo world'
hello
world

Done: After I figure out what that example in the Kubernetes Resource Model (KRM) Functions Specification Examples section means, then add another example where you actually run a kubectl, kustomize, or docker command. Edit: For an excellent guided Containerized KRM Functions example, see https://kubectl.docs.kubernetes.io/guides/extending_kustomize/containerized_krm_functions/#guided-example. For a presentation about KRM Functions, see https://youtu.be/YlFUv4F5PYc?t=997. For a live working session about KRM Functions, see https://youtu.be/iHhCssvnv6Y?t=1155. Edit: To learn about Kustomize plugins by example, see Kustomize plugins public gist.

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

/reopen

This is linked from the official docs for KRM functions.

Is there any way to formalize what "Alpha" status means here? It's been 2+ years...

@shakefu: You can't reopen an issue/PR unless you authored it or you are a collaborator.

/remove-lifecycle rotten

@KnVerey Thoughts on finalizing the current state as "v1" and letting a nebulous "v2" linger instead of keeping Alpha status forever?

@KnVerey can we have some clarity on the timeline for this feature to become stable or at least move to Beta. Thank you!

If @KnVerey is not active anymore with k8s, maybe someone can help us figure out if this is going to move forward or not? Or tag the correct person? /cc @logicalhan @xing-yang @Huang-Wei @palnabarun