Repository navigation
Standardize on using kubernetes.core instead of kubectl commands #574
Description
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
Activity
github-actions commentedon Mar 29, 2025
This issue is stale because it has been open 30 days with no activity.
bek-afs commentedon Mar 31, 2025
Is there any plan to address this feature request? My environment requires a proxy so I had to pull down my own version of this code, add in the code to support a proxy, and rebuild the image.
github-actions commentedon May 2, 2025
This issue is stale because it has been open 30 days with no activity.
bek-afs commentedon May 5, 2025
@saschjmil @dhoucgitter @riragh Tagging some folks from the development team. This request was opened ~8 months ago and haven't seen any responses so far. Will this request be considered for implementation at any point?
saschjmil commentedon May 5, 2025
@bek-afs We currently don't have any plans to implement this. However, you, @Andy-Tr, or anyone else is welcome to open a PR to make the change. I'll add a 'Help Wanted' label to signify that we are leaving it up to the community.
github-actions commentedon Jun 5, 2025
This issue is stale because it has been open 30 days with no activity.