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

Proxy support is not cascaded into the trustee deployment #68

Open
lmilleri opened this issue Jan 14, 2025 · 0 comments
Open

Proxy support is not cascaded into the trustee deployment #68

lmilleri opened this issue Jan 14, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@lmilleri
Copy link
Member

Describe the bug

Trustee Operator should inspect its environment for the standard proxy variables (HTTPS_PROXY, HTTP_PROXY, and NO_PROXY) and pass the values to trustee container(s).
The trustee-operator-controller-manager deployment is getting the proxy settings properly (when cluster-wide proxy settings are present), but the trustee-deployment is not.

How to reproduce

This bug has been reproduced in Openshift.
Steps:

  1. Configure the cluster-wide proxy (e.g. https://docs.openshift.com/container-platform/4.17/networking/enable-cluster-wide-proxy.html)
  2. Deploy the trustee operator

Issue: the linux standard PROXY env variables are not set in the trustee-deployment

CoCo version information

N.A.

What TEE are you seeing the problem on

None

Failing command and relevant log output

No response

@lmilleri lmilleri added the bug Something isn't working label Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant