Skip to content

fix(ingress-controller): use webhook secret name from values when provided#955

Open
nikaro wants to merge 1 commit intoapache:masterfrom
nikaro:unfair-shading
Open

fix(ingress-controller): use webhook secret name from values when provided#955
nikaro wants to merge 1 commit intoapache:masterfrom
nikaro:unfair-shading

Conversation

@nikaro
Copy link
Copy Markdown

@nikaro nikaro commented Mar 24, 2026

This PR fixes #954 by modifying the webhook.secretName helper to use the user-provided secret name from values.yaml when webhook.certificate.provided is true and webhook.certificate.secretName is set.

…vided

The webhook.certificate.secretName value in values.yaml was being ignored.
The deployment always used the helper-generated name regardless of user input.

This fix modifies the webhook.secretName helper to:
- Check if webhook.certificate.provided is true AND secretName is set
- Use the user-provided secret name when both conditions are met
- Fall back to the generated default otherwise

Fixes apache#954
@Baoyuantop Baoyuantop added the bug Something isn't working label Apr 9, 2026
@nikaro
Copy link
Copy Markdown
Author

nikaro commented Apr 20, 2026

Can this be reviewed/merged/released? 🥺

@Baoyuantop Baoyuantop requested review from AlinsRan and nic-6443 April 23, 2026 07:37
Copy link
Copy Markdown
Member

@nic-6443 nic-6443 left a comment

Choose a reason for hiding this comment

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

LGTM

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

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ingress-controller deployment does not use webhook secret name from values

3 participants