Skip to content

Fix indentation in webhook-deployment when both webhook.volumes and webhook.config is provided#8664

Merged
cert-manager-prow[bot] merged 1 commit into
cert-manager:masterfrom
jnohlgard:helm-webhook-deployment-indent
Mar 30, 2026
Merged

Fix indentation in webhook-deployment when both webhook.volumes and webhook.config is provided#8664
cert-manager-prow[bot] merged 1 commit into
cert-manager:masterfrom
jnohlgard:helm-webhook-deployment-indent

Conversation

@jnohlgard

Copy link
Copy Markdown
Contributor

Pull Request Motivation

#8010 broke the indentation in webhook-deployment.yaml when both webhook.config and webhook.volumes are defined.

helm template gives the following message with my current config:
Error: YAML parse error on cert-manager/templates/webhook-deployment.yaml: error converting YAML to JSON: yaml: line 99: did not find expected key

Specifically, these two unmotivated changed lines:

Kind

/kind bug

Release Note

Helm: Fix invalid YAML generated when both `webhook.config` and `webhook.volumes` are defined.

…ebhook.config is provided

Signed-off-by: Joakim Nohlgård <joakim@nohlgard.se>
@cert-manager-prow cert-manager-prow Bot added kind/bug Categorizes issue or PR as related to a bug. release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. area/deploy Indicates a PR modifies deployment configuration needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 30, 2026
@cert-manager-prow

Copy link
Copy Markdown
Contributor

Hi @jnohlgard. Thanks for your PR.

I'm waiting for a cert-manager member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@cert-manager-prow cert-manager-prow Bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 30, 2026
@erikgb erikgb requested a review from Copilot March 30, 2026 15:00
@erikgb

erikgb commented Mar 30, 2026

Copy link
Copy Markdown
Member

/ok-to-test

@cert-manager-prow cert-manager-prow Bot added ok-to-test and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 30, 2026

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 Helm chart rendering for the cert-manager webhook Deployment when both webhook.config and user-supplied webhook.volumeMounts/webhook.volumes are set, addressing the YAML parse error introduced in #8010.

Changes:

  • Adjust nindent for webhook.volumeMounts rendering so list items correctly nest under volumeMounts:.
  • Adjust nindent for webhook.volumes rendering so list items correctly nest under volumes:.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@erikgb erikgb left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@jnohlgard, thanks a lot! It looks indeed like #8010 introduced a regression. I have no idea how this apparently unrelated change slipped through our review. But Helm has a lot of sharp corners, and it is also very hard to use standard good software development principles like testing on Helm charts. 😓

I was able to reproduce the bug locally, and also that your patch fixes the issue. 🚀

We just had a patch release of cert-manager 1.20, but I am going to cherry-pick this fix into our release-1.20 branch to ensure it will be included in our first patch release.

/lgtm
/approve
/cherrypick release-1.20

@cert-manager-prow cert-manager-prow Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 30, 2026
@cert-manager-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: erikgb

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@cert-manager-prow cert-manager-prow Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 30, 2026
@cert-manager-prow cert-manager-prow Bot merged commit 2e45c01 into cert-manager:master Mar 30, 2026
10 checks passed
@erikgb

erikgb commented Mar 30, 2026

Copy link
Copy Markdown
Member

/cherrypick release-1.20

@cert-manager-bot

Copy link
Copy Markdown
Contributor

@erikgb: new pull request created: #8665

Details

In response to this:

/cherrypick release-1.20

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@erikgb

erikgb commented Apr 14, 2026

Copy link
Copy Markdown
Member

@jnohlgard, a fix for this regression has been released as part of cert-manager 1.20.2. Sorry for the inconvenience! 🙈

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/deploy Indicates a PR modifies deployment configuration dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. ok-to-test release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants