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
I understand that AWX Operator is open source software provided for free and that I might not receive a timely response.
Feature Summary
Currently as I deploy AWX on to a new EKS cluster with Kustomize I have to do this in 2 steps if I want to implement https on 443.
apply Kustoimize to deploy AWX on port 80
Update Kustomize with https, 443 and Certificate arn alb annotation and apply
The reason being that I cant create a route53 entry for my cert until the alb is provisioned by the ingress controller.
Only once the alb is provisioned can I then create a route53 entry pointing to it, and then create a certificate in AWS Certificate Manager... finally I can then update my Kustomize files to use 443, https and reference the certificate arn before applying a second time.
It would be nice if there was a way to run Kustomize only once to deploy AWX in this way, or am I misunderstanding something?
The text was updated successfully, but these errors were encountered:
Please confirm the following
Feature Summary
Currently as I deploy AWX on to a new EKS cluster with Kustomize I have to do this in 2 steps if I want to implement https on 443.
The reason being that I cant create a route53 entry for my cert until the alb is provisioned by the ingress controller.
Only once the alb is provisioned can I then create a route53 entry pointing to it, and then create a certificate in AWS Certificate Manager... finally I can then update my Kustomize files to use 443, https and reference the certificate arn before applying a second time.
It would be nice if there was a way to run Kustomize only once to deploy AWX in this way, or am I misunderstanding something?
The text was updated successfully, but these errors were encountered: