-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
2.4, 2.5
-
None
-
False
-
-
False
What is the nature and description of the request?
Without modifying Ansible Automation Platform's configuration, there is no way to connect to a container group through a HTTP proxy. There are two ways that Ansible Automation Platform contacts the OpenShift / Kubernetes cluster when launching a job on the container group.
- Automation Controller creates a temporary kubeconfig file (https://github.com/ansible/awx/blob/764dcbf94b51f9b55b467824208e4c8b9dc15786/awx/main/scheduler/kubernetes.py#L180-L198)
- Automation Controller sends the job metadata and files to `receptor` to have it send the job to OpenShift / Kubernetes
In the kubeconfig, there appears to be a way to specify a `proxy-url`.
Why does the customer need this? (List the business requirements here)
Customer is architecting their environment to have a container group in another environment that is only accessible through a HTTP proxy.
How would you like to achieve this? (List the functional requirements here)
- Add an option for HTTP proxies within the OpenShift / Kubernetes credential
List any affected known dependencies: Doc, UI etc..
- Automation Controller's OpenShift / Kubernetes credential and the documentation for credential
Github Links