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
ingress_path needs a * for GKE ingress #948
Comments
Without the patch, I tried to set |
@rooftopcellist Do we have any kind of "platform" tags that we could use for a Jinja |
We don't have any "platform" tags or variables to key off of, and I think we should avoid adding too much platform specific logic to the awx-operator if possible. After chatting on IRC the idea of adding an This variable should also be configurable via the spec. |
Hey @sdigit, Thank you for your already quite thorough post. I am facing the same issue, but my understanding of Kubernetes so far is limited so I haven't been able to resolve this. What I have done so far:
kustomization.yaml:
awx-deployment.yaml:
I removed the tls line as I want to get it running over http first and then move to https once it works. Result is a 502 and Kubernetes proclaims that the "Backend is unhealthy". Any steps I am missing to apply your fix and deploy AWX on GKE? Thank you so much for your time! |
I just had to redo this fix myself for
|
Please confirm the following
Bug Summary
On GKE, I use an HTTP(s) load balancer. In order for it to work, I needed to modify the ingress spec the operator creates to append a
/*
to it. SeeAdditional information
for the details.I'm happy to work on putting this into a proper PR, my question is how to do it - I understand that Google-specific settings are probably not desirable, does anyone have a suggestion?
AWX Operator version
0.22.0
AWX version
21.0.0
Kubernetes platform
other (please specify in additional information)
Kubernetes/Platform version
v1.21.11-gke.900
Modifications
yes
Steps to reproduce
Deploy AWX in GKE with an HTTP load balancer in front of it
Deployment will succeed, but AWX will never become usable as it won't be routing the correct path prefix.
Expected results
AWX to come up and work
Actual results
I needed to modify the operator to append a
/*
Additional information
Spec snippet:
The patch I created:
The final ingress looks like this:
Operator Logs
No response
The text was updated successfully, but these errors were encountered: