From 1f2849be5d36450aff7d0997f68d544542382a92 Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Tue, 14 Apr 2026 12:36:31 +0000 Subject: [PATCH] Fix: Update Helm charts MI version references to 4.6.0 for main branch Co-Authored-By: Claude Sonnet 4.5 --- .../setup/deployment/configuring-helm-charts.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/en/docs/install-and-setup/setup/deployment/configuring-helm-charts.md b/en/docs/install-and-setup/setup/deployment/configuring-helm-charts.md index 2a6af68e9..1e3fce50d 100644 --- a/en/docs/install-and-setup/setup/deployment/configuring-helm-charts.md +++ b/en/docs/install-and-setup/setup/deployment/configuring-helm-charts.md @@ -23,7 +23,7 @@ To get started: ```bash git clone https://github.com/wso2-enterprise/helm-mi.git cd helm-mi -git checkout 4.4.x +git checkout 4.6.x ``` Let's refer to the root folder of the local copy as ``. @@ -53,13 +53,13 @@ There may be scenarios where you need to create a customized base WSO2 Integrato The example below shows how to copy custom JARs into the MI runtime's `lib` directory: ```docker -FROM registry.wso2.com/wso2-integrator/mi:4.4.0 +FROM registry.wso2.com/wso2-integrator/mi:4.6.0 USER wso2carbon ARG USER_HOME=/home/${USER} ARG WSO2_SERVER_NAME=wso2mi -ARG WSO2_SERVER_VERSION=4.4.0 +ARG WSO2_SERVER_VERSION=4.6.0 ARG WSO2_SERVER=${WSO2_SERVER_NAME}-${WSO2_SERVER_VERSION} ARG WSO2_SERVER_HOME=${USER_HOME}/${WSO2_SERVER} @@ -227,7 +227,7 @@ Follow the steps below to secure the TOML configurations: ``` Once enabled, all the password values provided via the Helm chart must be in encrypted format. - Refer to the [`[secrets]` section](https://github.com/wso2/helm-mi/blob/4.4.x/mi/confs/deployment.toml#L204) of the `deployment.toml` to identify which values require encryption. + Refer to the [`[secrets]` section](https://github.com/wso2/helm-mi/blob/4.6.x/mi/confs/deployment.toml#L204) of the `deployment.toml` to identify which values require encryption. 2. Encrypt secret values. @@ -249,9 +249,9 @@ Follow the steps below to secure the TOML configurations: Refer to the following guides based on your cloud environment for detailed instructions: - - Amazon Elastic Kubernetes Service (EKS) - - Azure Kubernetes Service (AKS) - - Google Kubernetes Engine (GKE) + - Amazon Elastic Kubernetes Service (EKS) + - Azure Kubernetes Service (AKS) + - Google Kubernetes Engine (GKE) ## User store configurations @@ -467,6 +467,6 @@ This ensures that all generated resources follow the naming convention for easie ## What's next? -- To explore advanced configurations and vendor–specific cluster settings, refer to the Examples documentation and the Config documentation in the WSO2 Integrator: MI Helm Chart repository. +- To explore advanced configurations and vendor–specific cluster settings, refer to the Examples documentation and the Config documentation in the WSO2 Integrator: MI Helm Chart repository. - For a hands-on experience deploying WSO2 Integrator: MI and the Integration Control Plane (ICP) in a local Kubernetes cluster using commonly used configurations, see the [Sample Deployment]({{base_path}}/install-and-setup/setup/deployment/sample-k8s-deployment/) guide.