You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When a site requires a proxy server to access the K8S api from outside the cluster, multiple environment variables must be defined. The Ansible kubernetes core functions use K8S_AUTH_PROXY. The kubectl command uses HTTP_PROXY and HTTPS_PROXY.
Describe the solution you'd like
The deployment tool should standardize on using the Ansible kubernetes core functions instead of using kubectl commands directly. The K8S_AUTH_PROXY environment variable could then be passed when invoking the docker container.
Describe alternatives you've considered
Using both K8S_AUTH_PROXY and HTTP_PROXY/HTTPS_PROXY causes the SASDeployment CR to have proxy settings, which won't work inside the cluster. Customizations are required to support a proxy environment to pass the HTTP proxy values to the steps which still use kubectl.
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When a site requires a proxy server to access the K8S api from outside the cluster, multiple environment variables must be defined. The Ansible kubernetes core functions use K8S_AUTH_PROXY. The kubectl command uses HTTP_PROXY and HTTPS_PROXY.
Describe the solution you'd like
The deployment tool should standardize on using the Ansible kubernetes core functions instead of using kubectl commands directly. The K8S_AUTH_PROXY environment variable could then be passed when invoking the docker container.
Describe alternatives you've considered
Using both K8S_AUTH_PROXY and HTTP_PROXY/HTTPS_PROXY causes the SASDeployment CR to have proxy settings, which won't work inside the cluster. Customizations are required to support a proxy environment to pass the HTTP proxy values to the steps which still use kubectl.
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: