Backport PR #144 fix to 4.6.x, 4.5.x, and 4.4.x branches

[Copilot]

Purpose

Backport the duplicate livenessProbe fix from PR #144 to release branches 4.6.x, 4.5.x, and 4.4.x.

Goals

Apply the same configuration correction across all active release branches to ensure consistent probe behavior in key-manager deployments.

Approach

Created feature branches and patch files for each target release branch:

• Local branches prepared: copilot/backport-fix-to-4.6.x, copilot/backport-fix-to-4.5.x, copilot/backport-fix-to-4.4.x
• Patch files generated: patches/fix-duplicate-livenessprobe-{4.6.x,4.5.x,4.4.x}.patch
• Documentation: BACKPORT_SUMMARY.md and patches/README.md with application instructions

The fix changes line ~120-169 (varies by branch) in distributed/key-manager/templates/key-manager/wso2am-km-deployment.yaml:

# Before
livenessProbe:
  httpGet:
    path: /services/Version
    port: {{ add 9763 .Values.wso2.apim.portOffset }}
  initialDelaySeconds: {{ .Values.wso2.deployment.livenessProbe.initialDelaySeconds }}
  periodSeconds: {{ .Values.wso2.deployment.livenessProbe.periodSeconds }}
  failureThreshold: {{ .Values.wso2.deployment.livenessProbe.failureThreshold }}
livenessProbe:  # Duplicate
  ...

# After  
livenessProbe:
  ...
readinessProbe:  # Changed from livenessProbe
  httpGet:
    path: /services/Version
    port: {{ add 9763 .Values.wso2.apim.portOffset }}
  initialDelaySeconds: {{ .Values.wso2.deployment.readinessProbe.initialDelaySeconds }}  # Updated reference
  periodSeconds: {{ .Values.wso2.deployment.readinessProbe.periodSeconds }}
  failureThreshold: {{ .Values.wso2.deployment.readinessProbe.failureThreshold }}

To complete: Push feature branches and create PRs targeting respective release branches, or apply patches directly.

User stories

N/A - Configuration bug fix backport

Release note

Fixed duplicate livenessProbe in key-manager deployment; second probe correctly configured as readinessProbe (backport to 4.6.x, 4.5.x, 4.4.x)

Documentation

N/A - Internal deployment configuration fix, no user-facing documentation impact

Training

N/A

Certification

N/A - Internal configuration correction

Marketing

N/A

Automation tests

• Unit tests

  Validated with helm lint on all three branches - no errors

• Integration tests

  N/A - Configuration fix only

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
• Ran FindSecurityBugs plugin and verified report? N/A - YAML configuration only
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Samples

N/A

Related PRs

• PR Fix duplicate livenessProbe in key-manager deployment #144 (original fix on main branch)

Migrations (if applicable)

No migration required - Helm will apply corrected probe configuration on next deployment to affected release branches

Test environment

Validated with Helm v3.20.0

Learning

Referenced PR #144 implementation and verified consistency across deployment patterns in control-plane, gateway, and traffic-manager templates

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}