Skip to content
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

Merged
merged 2 commits into from Aug 14, 2018

Conversation

munnerz
Copy link
Member

@munnerz munnerz commented Aug 14, 2018

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 empty rule (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:

Fix issue causing existing Ingresses to not be cleaned up properly after HTTP01 challenges in some cases

@jetstack-bot jetstack-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Aug 14, 2018
@jetstack-bot jetstack-bot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Aug 14, 2018
Signed-off-by: James Munnelly <james.munnelly@jetstack.io>
Signed-off-by: James Munnelly <james.munnelly@jetstack.io>
@jetstack-bot jetstack-bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Aug 14, 2018
@munnerz
Copy link
Member Author

munnerz commented Aug 14, 2018

/cc @kragniz

Copy link
Contributor

@kragniz kragniz left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@jetstack-bot jetstack-bot added the lgtm Indicates that a PR is ready to be merged. label Aug 14, 2018
@jetstack-bot
Copy link
Collaborator

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jetstack-bot jetstack-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 14, 2018
@jetstack-bot jetstack-bot merged commit a0cb67f into cert-manager:master Aug 14, 2018
@luxflux
Copy link

luxflux commented Aug 17, 2018

Just came here to report this issue. Looking forward to the new release 馃槃
Thanks a lot for your work!

@freedomofkeima
Copy link

Same issue encountered here, looking forward to the next release, thank you! 馃帀

@Utwo
Copy link

Utwo commented Nov 2, 2018

Same here :(

alvaroaleman added a commit to kubermatic/kubermatic that referenced this pull request Jan 21, 2019
Fixes an issue where a not properly cleaned up Ingress causes the next
certificate order to fail cert-manager/cert-manager#831
kubermatic-bot pushed a commit to kubermatic/kubermatic that referenced this pull request Jan 21, 2019
Fixes an issue where a not properly cleaned up Ingress causes the next
certificate order to fail cert-manager/cert-manager#831
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. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ingress not cleaned up after certificate is issued
6 participants