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

Setting environment variables in userdata #5217

Open
ethanchowell opened this issue Nov 18, 2024 · 1 comment
Open

Setting environment variables in userdata #5217

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

Comments

@ethanchowell
Copy link

/kind feature

Describe the solution you'd like
I'd like to be able to set environment variables for the userdata that is pulling from secrets manager. In our environments we have to access secretsmanager through an HTTP_PROXY and set a few environment variables for things like AWS_CA_BUNDLE and some service endpoints. As is I'm not aware of a way to do this with the existing config.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Cluster-api-provider-aws version: clusterawsadm version: &version.Info{Major:"2", Minor:"6", GitVersion:"2.6.1", GitCommit:"6db1244a6aea9058cc0546dd7d2151fc2c624acc", GitTreeState:"clean", BuildDate:"2024-07-30T08:09:15Z", GoVersion:"go1.21.12", AwsSdkVersion:"v1.51.17", Compiler:"gc", Platform:"linux/amd64"}
  • Kubernetes version: (use kubectl version):
Client Version: v1.27.9
Kustomize Version: v5.0.1
Server Version: v1.30.0
  • OS (e.g. from /etc/os-release):
$ cat /etc/os-release 
NAME="Red Hat Enterprise Linux"
VERSION="8.10 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.10"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux 8.10 (Ootpa)"
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 18, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

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.

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-priority 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