I’m already using istio installed using helm and I am looking to move forward to using the operator.
At the moment, the operator installs different components (pilot, citadel, mixer, etc.) based on a CR
IstioControlPlane and manages the reconciliation. But I think it needs more flexibility when it comes to gateways - now it only supports an ingress and an egress gateway-controller deployment.
I feel like for this part there should be a different CR (maybe
IstioGatewayController) to manage a deployment for a specific istio-gateway-controller.
apiVersion: install.istio.io/v1alpha2 kind: IstioGatewayController metadata: name: my-demo-project-ingress namespace: demo spec: resources: ... ports: ... ...
In my use case, each namespace is used by a project (or a team) and I would like to be able to create one or more instances of ingress-controller in each one. I think this way we have a better separation of concerns for every project and it comes with many more advantages.
Is there a way to use the current operator implementation in my scenario? Or are there any plans to improve in this direction?
PS: I’m not sure if I should have posted it here instead