New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix issue causing existing ingresses to not be cleaned up properly #831
Conversation
b5bc173
to
2c433d4
Compare
Signed-off-by: James Munnelly <james.munnelly@jetstack.io>
Signed-off-by: James Munnelly <james.munnelly@jetstack.io>
eca8651
to
22f5d8c
Compare
/cc @kragniz |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kragniz The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Just came here to report this issue. Looking forward to the new release 馃槃 |
Same issue encountered here, looking forward to the next release, thank you! 馃帀 |
Same here :( |
Fixes an issue where a not properly cleaned up Ingress causes the next certificate order to fail cert-manager/cert-manager#831
Fixes an issue where a not properly cleaned up Ingress causes the next certificate order to fail cert-manager/cert-manager#831
What this PR does / why we need it:
Previously, if an ingress resource did not specify an existing
rule
containing the domain name we need to solve for (e.g. if only the default backend is configured), we would leave an emptyrule
(one with any path configuration) which would consequently fail validation when submitting back to the apiserver.This patch fixes this so we remove empty rules after cleaning up. It also adds a unit test to verify the behaviour. The newly added unit test fails without the second commit applied 馃槃
The actual ingress test fixture for this was taken from聽#828.
Which issue this PR fixes: fixes #828
Release note: