404 page not found

[SorenSj]

404 page not found

[kurokobo]

@passe4wedo
There is service_type parameter instead of ingress_type to expose your service via NodePort or LoadBalancer. Note that NodePort has an issue with not being able to specify a port(ansible/awx-operator#788), so you should wait for the next release if you want to use fixed port for NodePort.

But if you create an Ingress through AWX Operator on EKS, the ALB will be used as actual implementation, so you can manage it through AWX Operator by using ingress_annotations and other params, instead of deploying Ingress yourself.

[SorenSj]

It's working! Thanks a lot :-)

[kurokobo]

Access AWX via hostname instead of IP address. Kubernetes routes your HTTP trafic according to the HOST header in the HTTP request.

Therefore, if you specify awx.example.com as described in my repo,

...
spec:
  ...
  ingress_type: ingress
  ingress_tls_secret: awx-secret-tls
  hostname: awx.example.com     👈👈👈
...

your AWX can be accessed via https://awx.example.com instead of IP address. So you should configure your DNS or hosts file on your client (where the brower is running).

[passe4wedo]

Is there the possibility to expose the service in order to access it by using the IPAddress:Port only?
It would be useful for the integration of managed load balancers such as AWS ALB (for health check purposes and external certificate management).