Fix/k8s deployment 470#11330
Conversation
- Bump version references: 4.6.0 → 4.7.0, 4.6.x → 4.7.x, chart version 4.6.0-1 → 4.7.0-1 - Update Docker registry: docker.wso2.com → registry.wso2.com with new image path format (wso2-apim/am, wso2-apim/am-acp, etc.) - Change default Kubernetes namespace from wso2 to apim - Rename Step 4 to "Install a Routing Controller" with Envoy Gateway as default tab and NGINX as legacy - Update DNS step to include Gateway API note and kubectl get gateway/ing sub-tabs - Update Access Portals step with Envoy Gateway and NGINX tabs - Rename Section 4 from "Ingress" to "Routing Controller" with Envoy Gateway (4.1) and NGINX (4.2) - Add mandatory internal encryption key section (3.2) to pattern-0 and pattern-6 - Update AWS Secrets Manager YAML to new nested secretsManager.secretIdentifiers.secretEncryptionKey structure Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Rename Step 2 to "Install a Routing Controller" with Envoy Gateway as default and NGINX as legacy - Update helm install: version 4.6.0-1 → 4.7.0-1, namespace wso2 → apim, branch 4.6.x → 4.7.x - Update DNS step to show kubectl get gateway / kubectl get ing tabs per routing controller - Remove hardcoded wso2 namespace from kubectl commands Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…-470 # Conflicts: # en/docs/install-and-setup/setup/kubernetes-deployment/kubernetes/am-pattern-0-all-in-one.md # en/docs/install-and-setup/setup/kubernetes-deployment/kubernetes/am-pattern-1-all-in-one-ha.md # en/docs/install-and-setup/setup/kubernetes-deployment/kubernetes/am-pattern-2-all-in-one-gw.md # en/docs/install-and-setup/setup/kubernetes-deployment/kubernetes/am-pattern-3-acp-tm-gw.md # en/docs/install-and-setup/setup/kubernetes-deployment/kubernetes/am-pattern-4-acp-tm-gw-km.md # en/docs/install-and-setup/setup/kubernetes-deployment/kubernetes/am-pattern-5-all-in-one-gw-km.md # en/docs/install-and-setup/setup/kubernetes-deployment/kubernetes/am-pattern-6-all-in-one-is-as-km.md
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Purpose
Rewrites the WSO2 API Manager 4.7.0 Kubernetes deployment documentation for all seven deployment patterns (Patterns 0–6). The previous docs had broken references, incorrect Dockerfile instructions, missing prerequisites, outdated step structures, and several configuration errors introduced in 4.7.0 that would cause deployments to fail.
Resolves https://github.com/wso2-enterprise/wso2-apim-internal/issues/16522
Goals
backendTrafficPolicyblock (sticky sessions for HA patterns)aws.enabled: truefield in the AWS Secrets Manager YAML (not a valid field)wso2internal.jksfrom the keystore secret creation commandsApproach
Each pattern doc was rewritten end-to-end with a consistent Quick Start structure followed by an Additional Configuration section. Changes were verified against the upstream Helm chart (
helm-apim 4.7.0-1) and the 4.7.0 configuration reference. Key structural improvements include:backendTrafficPolicyadded to all HA pattern Envoy Gateway YAML blocks (Patterns 1–6)enabled: truefieldwso2internal.jksadded todocker runextract commands andkubectl create secretcommands in all patternsUser stories
Release note
Updated Kubernetes deployment documentation for WSO2 API Manager 4.7.0 — rewrote all seven pattern guides with corrected configuration examples, Envoy Gateway as default routing controller, and fixed keystore and encryption key setup instructions.
Documentation
This PR is the documentation change. N/A for additional doc links.
Training
N/A — no training content impact.
Certification
N/A — documentation-only change with no impact on certification exam topics.
Marketing
N/A
Automation tests
Security checks
Samples
N/A
Related PRs
N/A
Migrations
N/A
Learning
N/A