|
| 1 | +:_mod-docs-content-type: CONCEPT |
| 2 | + |
| 3 | +[id="compare-the-helm-chart-and-operator-to-choose-the-optimal-deployment-method_{context}"] |
| 4 | += Compare the Helm chart and Operator to choose the optimal deployment method |
| 5 | + |
| 6 | +[role="_abstract"] |
| 7 | +When planning your {product} deployment, you must choose between the Helm chart and Operator installation methods. Use the following table to choose the method that aligns with your operational model and team capabilities: |
| 8 | + |
| 9 | +[cols="1,1",options="header"] |
| 10 | +|=== |
| 11 | +|Helm chart |Operator |
| 12 | + |
| 13 | +a|*Platform requirements* |
| 14 | + |
| 15 | +* You deploy across multiple Kubernetes platforms ({eks-short}, {gke-short}, {aks-short}). |
| 16 | +* You need maximum portability across different environments. |
| 17 | +a|*Platform requirements* |
| 18 | + |
| 19 | +* You primarily use {ocp-short}. |
| 20 | +* Your platform has Operator Lifecycle Manager (OLM) installed. |
| 21 | + |
| 22 | +a|*Setup and deployment priorities* |
| 23 | + |
| 24 | +* You want the simplest initial setup. |
| 25 | +* You prefer fewer deployment steps to get started. |
| 26 | +* You are familiar with Helm workflows. |
| 27 | +a|*Setup and deployment priorities* |
| 28 | + |
| 29 | +* You prioritize long-term automation over initial simplicity. |
| 30 | +* You accept more initial setup complexity for ongoing operational benefits. |
| 31 | +* You want integrated lifecycle management from the start. |
| 32 | + |
| 33 | +a|*Update preferences* |
| 34 | + |
| 35 | +* You want full control over update timing. |
| 36 | +* You test updates in stages across environments. |
| 37 | +* You manage updates manually on your schedule. |
| 38 | +a|*Update preferences* |
| 39 | + |
| 40 | +* You want automated update availability through subscription channels. |
| 41 | +* You prefer continuous reconciliation of desired state. |
| 42 | +* You want less operational overhead for maintaining {product-short}. |
| 43 | + |
| 44 | +a|*Team capabilities* |
| 45 | + |
| 46 | +* Your team has Helm expertise. |
| 47 | +* You want direct access to Kubernetes resources. |
| 48 | +* You prefer hands-on management and troubleshooting. |
| 49 | +a|*Team capabilities* |
| 50 | + |
| 51 | +* Your team follows Kubernetes-native Operator patterns. |
| 52 | +* You want built-in lifecycle management. |
| 53 | +* You are comfortable working with custom resources. |
| 54 | + |
| 55 | +a|*Control and customization needs* |
| 56 | + |
| 57 | +* You need direct control over all Kubernetes resources. |
| 58 | +* You want full visibility into generated manifests. |
| 59 | +* You prefer to inspect and modify deployed resources directly. |
| 60 | +a|*Control and customization needs* |
| 61 | + |
| 62 | +* You prefer declarative configuration through custom resources. |
| 63 | +* You want validation and reconciliation by the Operator. |
| 64 | +* You value standardized deployment patterns across your organization. |
| 65 | + |
| 66 | +|=== |
| 67 | + |
| 68 | +Both installation methods are fully supported by Red Hat. Choose the method that best matches your operational priorities, platform requirements, and team expertise. |
| 69 | + |
| 70 | +For detailed installation instructions, see {installing-on-ocp-book-link}[{installing-on-ocp-book-title}]. |
0 commit comments