Deploying plural on existing GCP cluster using Gateway + Istio

[rogaha]

What content is missing

I am seeking a detailed guide or documentation on how to deploy Plural on an existing Google Cloud Platform (GCP) Kubernetes cluster that utilizes Gateway and Istio for ingress and service mesh functionalities. The available resources mainly cover deployments on new clusters or without specific ingress configurations. I need step-by-step instructions on integrating Plural into my current setup, including configuring Istio and Gateway to work seamlessly with Plural.

Type of the content

• Deployment Guide
• Integration Documentation
• Step-by-Step Tutorial

Anything else?

Please include any prerequisites, configuration examples, and best practices. Information on potential challenges and how to troubleshoot common issues during the deployment process would be highly valuable. Additionally, insights into security considerations and performance optimizations in this context would be appreciated.

[michaeljguarino]

Hey, are you looking to deploy the plural console? We currently just use an ingress resource, which could use istio's ingress controller w/ a helm configuration change. I think there might be some consequences related to the erlang clustering we use internally though.

That said, you usually place Plural in a dedicated management cluster, it's not always advisable to place them in a multi-tenant cluster more from a security and architectural perspective, which is where istio shines.

[rogaha]

Hey @michaeljguarino, thanks for the quick reply. I'm using k8s Gateway with istio's gateway-controller. I want to deploy plural on this existing cluster, without using the ingress resources. I'm not deploying this in a multi-tenant environment. I'm running only my own infrastructure.