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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove BackupReady condition #867

Open
unmarshall opened this issue Aug 30, 2024 · 0 comments
Open

Remove BackupReady condition #867

unmarshall opened this issue Aug 30, 2024 · 0 comments
Labels
area/monitoring Monitoring (including availability monitoring and alerting) related area/usability Usability related kind/cleanup Something that is not needed anymore and can be cleaned up
Milestone

Comments

@unmarshall
Copy link
Contributor

How to categorize this issue?

/area monitoring
/area usability
/kind cleanup

What would you like to be added:
v0.24.0 release of etcd-druid will include deprecation of BackupReady condition. Purpose of this issue is to remove this condition as part of v0.27.0 milestone (3 minor releases post deprecation).

NOTE: Please check if there is any impact on removing this field in g/g or any other consumer.

Why is this needed:
Remove deprecated BackupReady condition in favour of FullSnapshotBackupReady and DeltaSnapshotBackupReady conditions.

@unmarshall unmarshall added this to the v0.27.0 milestone Aug 30, 2024
@gardener-robot gardener-robot added area/monitoring Monitoring (including availability monitoring and alerting) related area/usability Usability related kind/cleanup Something that is not needed anymore and can be cleaned up labels Aug 30, 2024
@unmarshall unmarshall changed the title Remove BackupReady condition (post deprecation period expiry) Remove BackupReady condition Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/monitoring Monitoring (including availability monitoring and alerting) related area/usability Usability related kind/cleanup Something that is not needed anymore and can be cleaned up
Projects
None yet
Development

No branches or pull requests

2 participants