Skip to content

Conversation

@shreddedbacon
Copy link
Member

@shreddedbacon shreddedbacon commented Mar 4, 2024

Checklist

  • Affected Issues have been mentioned in the Closing issues section
  • Documentation has been written/updated
  • PR title is ready for changelog and subsystem label(s) applied

Supports the existence of a kind: ConfigMap that contains data["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

@shreddedbacon shreddedbacon added this to the v1beta1 deprecation milestone Mar 4, 2024
@shreddedbacon shreddedbacon changed the base branch from main to main-v1beta2 May 2, 2024 06:45
@shreddedbacon shreddedbacon force-pushed the namespace-expiry-configmap branch 2 times, most recently from 0ac371b to 59bb795 Compare July 29, 2024 01:07
Base automatically changed from main-v1beta2 to main November 1, 2024 09:32
An error occurred while trying to automatically change base from main-v1beta2 to main November 1, 2024 09:32
@shreddedbacon shreddedbacon force-pushed the namespace-expiry-configmap branch from 59bb795 to 17c0fce Compare December 30, 2024 21:59
@shreddedbacon shreddedbacon force-pushed the namespace-expiry-configmap branch from 17c0fce to 0339bc0 Compare January 29, 2025 22:34
@shreddedbacon shreddedbacon force-pushed the namespace-expiry-configmap branch from 0339bc0 to bdf7931 Compare November 19, 2025 23:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants