Skip to content

docs: Fix mutatingWebhookTimeoutSeconds default in the README#4490

Open
zephyrdb wants to merge 1 commit into
open-policy-agent:masterfrom
mongodb-forks:fix-mutatingWebhookTimeoutSeconds-readme
Open

docs: Fix mutatingWebhookTimeoutSeconds default in the README#4490
zephyrdb wants to merge 1 commit into
open-policy-agent:masterfrom
mongodb-forks:fix-mutatingWebhookTimeoutSeconds-readme

Conversation

@zephyrdb

@zephyrdb zephyrdb commented Apr 3, 2026

Copy link
Copy Markdown

What this PR does / why we need it:

The default value for mutatingWebhookTimeoutSeconds is incorrect in the README.

See

mutatingWebhookTimeoutSeconds: 1

Maybe the whole thing needs to be regenerated from the chart, though?

@zephyrdb zephyrdb requested a review from a team as a code owner April 3, 2026 22:48
Copilot AI review requested due to automatic review settings April 3, 2026 22:48
@linux-foundation-easycla

linux-foundation-easycla Bot commented Apr 3, 2026

Copy link
Copy Markdown

CLA Not Signed

Signed-off-by: Danielle Zephyr Malament <danielle.zephyr@mongodb.com>
@zephyrdb zephyrdb force-pushed the fix-mutatingWebhookTimeoutSeconds-readme branch from 74fe2be to 0c5cfcf Compare April 3, 2026 22:49

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes an incorrect documented default for the Helm chart value mutatingWebhookTimeoutSeconds in the Gatekeeper chart README so that it matches the actual default in values.yaml.

Changes:

  • Update mutatingWebhookTimeoutSeconds default in charts/gatekeeper/README.md from 3 to 1.

| mutatingWebhookObjectSelector | The label selector to further refine which namespaced resources will be selected by the webhook. Please note that an exemption label means users can circumvent Gatekeeper's mutation webhook unless measures are taken to control how exemption labels can be set. | `{}` |
| mutatingWebhookMatchConditions | The match conditions written in CEL to further refine which resources will be selected by the webhook. All match conditions must evaluate to true for the webhook to be called | `[]` |
| mutatingWebhookTimeoutSeconds | The timeout for the mutating webhook in seconds | `3` |
| mutatingWebhookTimeoutSeconds | The timeout for the mutating webhook in seconds | `1` |

Copilot AI Apr 3, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This updates the default here to 1, but the generated chart docs still show mutatingWebhookTimeoutSeconds default as 3 in cmd/build/helmify/static/README.md (copied into manifest_staging/charts/gatekeeper/README.md by cmd/build/helmify/main.go). This creates inconsistent documentation within the repo and future chart regeneration is likely to revert this value back to 3 unless the static/template README is also updated.

Copilot uses AI. Check for mistakes.

@JaydipGabani JaydipGabani left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to update README here -

| mutatingWebhookTimeoutSeconds | The timeout for the mutating webhook in seconds | `3` |
, and revert this change. This will be updated with the release.

After the change in the linked file, you need to run make manifests generate so that the same change appears under manifest_staging/charts/gatekeeper/README.md and then push the changes.

Also, can you do easyCLA as well for the CI to turn green. Thanks for noticing this and fixing it.

@ogulcanaydogan ogulcanaydogan left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked values.yaml, default is indeed 1. README was out of sync. LGTM.

@github-actions

Copy link
Copy Markdown
Contributor

This PR has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

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.

4 participants