Deploy and upgrade all the components in Instana Backend on Openshift with a single Operator

We have published the installation script, you can check it here https://www.ibm.com/docs/en/instana-observability/1.0.312?topic=edition-installing-custom-shce-script

Publishing and documenting the Helm charts will take longer, so I will set this as "in development"

Thank you for sharing this idea and highlighting the business impact. We completely understand the importance of simplifying installation and upgrade processes, especially for large environments.

At some point, we explored the concept of a single Operator to manage all Instana backend components on OpenShift. However, we decided not to pursue this approach for several reasons:

• Complexity and Maintainability: A top-level Operator managing multiple components introduces significant complexity. When issues occur (e.g., with ClickHouse), troubleshooting and recovery become harder because everything is tied together.

• Component Independence: Large enterprises often need the ability to manage and restart individual components independently. A single Operator limits this flexibility.

• Customer-Specific Pipelines: Many customers prefer integrating Helm charts into their own CI/CD pipelines. This approach gives them control and aligns with their internal processes.

Instead, we are working on a different approach that will deliver similar benefits without the drawbacks:

• We will soon release a script that supports both installation and updates for Custom Edition.

• We plan to document and make all Helm charts publicly available, giving customers flexibility to adapt to their delivery pipelines while simplifying operations.

I’ll keep this idea open for now and share more details as soon as the script and documentation are ready. Our goal is to provide a solution that balances simplicity with flexibility for enterprise environments.