Skip to content

EPMDEDP-17309: docs: Document the Capsule 0.14 metadata webhook delet… - #431

Open
geekhubuser wants to merge 1 commit into
mainfrom
EPMDEDP-17309
Open

geekhubuser wants to merge 1 commit into
mainfrom
EPMDEDP-17309

Conversation

@geekhubuser

Copy link
Copy Markdown
Contributor

Pull Request Template

Description

Document the extra match condition that Capsule 0.14 needs, on the Install Capsule page (docs/operator-guide/advanced-installation/capsule.md).

  • Installation, step 1: the values example moves from the deprecated capsuleUserGroups to users, the key Capsule 0.14 expects.
  • Installation, new step 2: the webhooks.hooks.metadata.matchConditions values, and a warning that explains what breaks without them. Roles and RoleBindings created before Capsule 0.14 get stuck in Terminating when Argo CD deletes them, which covers stage deployments that prune, deleted environments, and Roles removed from application charts.
  • Step 3: notes that the Capsule add-on in Cluster Add-Ons already includes the condition.
  • Troubleshooting: how to find stuck Roles and RoleBindings on a cluster that has already upgraded, and how to release them.
  • projectcapsule and subresources added to cspell.config.yaml.

This belongs on the Capsule page rather than in an upgrade guide: it depends on the Capsule version a cluster runs, not on a KubeRocketCI release, and it applies to new installations and Capsule upgrades alike. The 3.16 upgrade guide can link to this section when it is written.

Jira: EPMDEDP-17309

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Enhancement (non-breaking change which improves an existing feature or documentation)
  • Breaking change (fix or feature that would cause existing functionality not to work as expected)

How Has This Been Tested?

  • cspell on the changed page: 0 issues.
  • The match conditions are the ones running on our sandbox cluster with Capsule 0.14.3, and both examples match the Cluster Add-Ons pull request.
  • Both troubleshooting commands were run against that cluster as written: the listing command, and the finalizer patch as a server-side dry run on a chart-managed RoleBinding.
  • npm ci and npm run build complete with no errors, warnings or broken links.
  • Served locally, the 3.16-dev page renders the three installation steps as one numbered list with the warning inside step 2, the Troubleshooting headings and anchors, and both commands with their escapes intact. The released 3.15 and 3.14 pages are unchanged.

Checklist:

  • I have performed a self-review of my code
  • I have commented on my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Pull Request contains one commit. I squash my commits.

Screenshots (if appropriate):

Additional context

Pairs with the epam/edp-cluster-add-ons pull request for the same ticket, which upgrades the Capsule add-on to 0.14.3 with this condition.

…ion guard

Capsule 0.14 needs an extra match condition on its metadata webhook, otherwise
Roles and RoleBindings created before the upgrade get stuck in Terminating when
Argo CD deletes them. Add the values to the installation steps, explain what
fails without them, and add a troubleshooting entry for clusters that have
already upgraded.

Move the installation example from the deprecated capsuleUserGroups to users,
which Capsule 0.14 expects.
@geekhubuser
geekhubuser requested a review from a team as a code owner September 11, 2026 08:10
@github-actions

Copy link
Copy Markdown

Azure Static Web Apps: Your stage site is ready! Visit it here: https://gentle-pebble-0839af61e-431.westus2.4.azurestaticapps.net

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant