Awesome, surely I will give it a try.
Cool! We would like to hear about your test results.
One last question I have about exposing the UI using a Kubernetes Load Balancer instead of listening on port localhost. Do we have a way for this as well?
Yes. Since this is an EKS cluster I can think of 3 ways to do this:
-
.spec.ingress_type: loadbalancer
the operator will create a k8s Service of typeLoadBalancer
(the k8s integration with the cloud provider will create the lb for you) -
.spec.ingress_type: ingress
the operator will deploy a k8s Ingress resource with the defined IngressController (more info in Reverse Proxy - Pulp Operator). -
.spec.ingress_type: nodeport
the operator will create a k8s Service typeNodePort
and you will need to manually create the AWS LoadBalancer to point to the k8s <nodes>:<node-port>