Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support scripting KRM functions #5808

Open
2 tasks done
guettli opened this issue Nov 24, 2024 · 1 comment
Open
2 tasks done

Support scripting KRM functions #5808

guettli opened this issue Nov 24, 2024 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@guettli
Copy link

guettli commented Nov 24, 2024

Eschewed features

  • This issue is not requesting templating, unstuctured edits, build-time side-effects from args or env vars, or any other eschewed feature.

What would you like to have added?

It would be great, if kustomize would include a scripting language for writing KRM functions.

These languages have a pure Go implementation: JS, starlark, Lua, cue.

Of course I could use Containerized KRM Functions but somehow an embedded language would feel more natural and lightweight to me.

Additionally, in air gapped environments it might be not possible to execute a container.

Why is this needed?

Sometimes I would like to do modifications which are not possible with an existing transformer.

Can you accomplish the motivating task without this feature, and if so, how?

I could use a Containerized KRM Functions.

What other solutions have you considered?

I could use Exec and a Bash script.

Anything else we should know?

Thank you for kustomize!

Feature ownership

  • I am interested in contributing this feature myself! 🎉
@guettli guettli added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 24, 2024
@k8s-ci-robot
Copy link
Contributor

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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants