feat: support namespace expiry configmap #251
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shreddedbacon
force-pushed
the
namespace-expiry-configmap
branch
from
2b3f0a0 to
0ac371b
Compare
shreddedbacon
force-pushed
the
namespace-expiry-configmap
branch
from
0ac371b to
59bb795
Compare
An error occurred while trying to automatically change base from
main-v1beta2
to
main
November 1, 2024 09:32
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
Supports the existence of a
kind: ConfigMapthat containsdata["timestamp']in the same format that the namespace timestamp label would contain. The standard namespace terminator cronjob will check for this and then check the namespace labels.If the configmap exists, it will prefer this over the namespace label.
Closing issues