adds [email protected]

[majodev]

envx - Extract and inject Kubernetes environment variables

This PR adds the envx plugin that helps extract environment variables from Kubernetes resources and optionally injects them into local commands.

• ✅ Make sure you read the Plugin Naming Guide: https://krew.sigs.k8s.io/docs/developer-guide/develop/naming-guide/
  • env + x for extract/execute
  • short, descriptive, action-oriented
  • an official kubectl subcommand will typically use kubectl view env or kubectl env - thus should be safe.
• ✅ Verified I can install envx locally: kubectl krew install --manifest=plugins/envx.yaml

Key features:

• Lists environment variables from any Kubernetes resource
• Resolves envFrom references (ConfigMaps and Secrets) - a current limitation of kubectl set env --resolve --list
• Supports variable overrides
• Can execute commands with extracted variables
• Works with Pods, Deployments, StatefulSets, CronJobs, etc.

Requirements:

• bash, sed, kubectl, jq
• Supports Linux and macOS

Dep	Supported Versions
kubectl	1.28, 1.29, 1.30, 1.31, 1.32
jq	1.6, 1.7.1
bash	5.2
(GNU) sed	4.9

Both Linux and MacOS tested.

Examples:

# Print all environment variables of a resource, e.g.
kubectl envx deployment/myapp
kubectl envx pod/myapp
kubectl envx job/myapp
kubectl envx cronjob/myapp
kubectl envx daemonset/myapp

# Print variables from specific namespace and container
kubectl envx deployment/myapp -n prod -c nginx

# Override variables
kubectl envx deployment/myapp DEBUG=true API_URL=http://localhost:8080

# Run command with variables
kubectl envx deployment/myapp -- env

# Use with docker (e.g. to run a local container with the extracted ENV variables)
# Note: This example uses process substitution, which is a bash feature.
# If you are using a different shell, you can save the output of `kubectl envx` to a file and use `--env-file` instead.
docker run --env-file <(kubectl envx deployment/postgres) -it alpine env

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: majodev / name: Mario Ranftl (6dbc846, 7ed42e5)

[ahmetb]

🤖 Beep beep! I’m a robot speaking on behalf of @ahmetb. 🤖

---

Thanks for submitting your kubectl plugin to Krew!
One of the krew-index maintainers will review it soon. Note that the reviews for new plugin submissions may take a few days.

In the meanwhile, here are a few tips to make your plugin manifest better:

• Make sure your plugin follows the best practices.
• Eliminate redundant wording form shortDescription (it should be max 50 characters).
• Try to word wrap your description to 80-character lines (no usage examples, please).

Thanks for your patience!
/kind new-plugin

[k8s-ci-robot]

Welcome @majodev!

It looks like this is your first PR to kubernetes-sigs/krew-index 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/krew-index has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[ahmetb]

/lgtm
/approve
Thanks!
Also, please consider setting up Krew release automation which helps you skip manually making updates to your Krew manifests on each new version and send a pull request. It’s a GitHub workflow bot that can run every time you push a new tag. Those PRs are automatically approved.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahmetb, majodev

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ahmetb]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment