Upgrade Gateway to v1.0.4

Instructions Important Notes If custom parameters were set during installation, make sure to back up and reset them during the upgrade: helm get values -n kubesphere-system ks-core | grep -v 'USER-SUPPLIED VALUES' > bak-values.yaml Step 1: Update the Extension Component Repository # Without custom parameters helm upgrade --install -n kubesphere-system --create-namespace ks-core https://charts.kubesphere.io/main/ks-core-1.1.4.tgz --debug --wait --set ksExtensionRepository.image.tag=v1.1.4 # With custom parameters helm upgrade --install -n kubesphere-system --create-namespace ks-core https://charts.kubesphere.io/main/ks-core-1.1.4.tgz --debug --wait -f bak-values.yaml --set ksExtensionRepository.image.tag=v1.1.4 Step 2: Trigger the Extension Component Repository Update kubectl patch repository extensions-museum --type=json -p='[{"op": "replace", "path": "/status", "value": {}}]' Update Gateway version to v1.0.4 Update the extension component configuration Paste the configuration from the Overview -> Upgrade section into the extension component configuration update box Step 3: Upgrade Gateway to Version v1.0.4 After the upgrade, update the Gateway extension component configuration according to the "Upgrade" section on the extension component page. Restart Gateway API Server kubectl rollout restart deploy -n extension-gateway gateway-agent-backend-apiserver Update Existing Gateway If the Gateway is already enabled in the cluster, the update will cause service interruptions. Please schedule an update window in advance. 1. Backup Gateway Configuration Go to the Gateway details page, click Edit, and record the current custom configuration. 2. Record the nodePort (If Port Consistency is Needed) In Application Load > Services, locate the Gateway service under kubesphere-controls-system, and record the nodePort port. 3. Disable the Gateway Click Disable on the Gateway details page. Note: This step will cause service interruptions. 4. Re-enable the Gateway If custom configurations exist, please reset them to ensure that the nodePort remains consistent (use the "Edit YAML" option to configure if necessary). Check Nginx Ingress Version Make sure the version is: kubesphere-nginx-ingress-4.12.1

Apr 7, 2025 - 07:31

Instructions

Important Notes

If custom parameters were set during installation, make sure to back up and reset them during the upgrade:

helm get values -n kubesphere-system ks-core | grep -v 'USER-SUPPLIED VALUES' > bak-values.yaml

Step 1: Update the Extension Component Repository

# Without custom parameters
helm upgrade --install -n kubesphere-system --create-namespace ks-core https://charts.kubesphere.io/main/ks-core-1.1.4.tgz --debug --wait --set ksExtensionRepository.image.tag=v1.1.4

# With custom parameters
helm upgrade --install -n kubesphere-system --create-namespace ks-core https://charts.kubesphere.io/main/ks-core-1.1.4.tgz --debug --wait -f bak-values.yaml --set ksExtensionRepository.image.tag=v1.1.4

Step 2: Trigger the Extension Component Repository Update

kubectl patch repository extensions-museum --type=json -p='[{"op": "replace", "path": "/status", "value": {}}]'

Update Gateway version to v1.0.4

Update the extension component configuration

Paste the configuration from the Overview -> Upgrade section into the extension component configuration update box

Step 3: Upgrade Gateway to Version v1.0.4

After the upgrade, update the Gateway extension component configuration according to the "Upgrade" section on the extension component page.

Restart Gateway API Server

kubectl rollout restart deploy -n extension-gateway gateway-agent-backend-apiserver

Update Existing Gateway

If the Gateway is already enabled in the cluster, the update will cause service interruptions. Please schedule an update window in advance.

1. Backup Gateway Configuration

Go to the Gateway details page, click Edit, and record the current custom configuration.

2. Record the nodePort (If Port Consistency is Needed)

In Application Load > Services, locate the Gateway service under kubesphere-controls-system, and record the nodePort port.

3. Disable the Gateway

Click Disable on the Gateway details page.

Note: This step will cause service interruptions.

4. Re-enable the Gateway

If custom configurations exist, please reset them to ensure that the nodePort remains consistent (use the "Edit YAML" option to configure if necessary).

Check Nginx Ingress Version

Make sure the version is:

kubesphere-nginx-ingress-4.12.1