You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 22, 2023. It is now read-only.
For Kubernetes objects created by Waiter, we should be using the namespace/property naming convention for all of our Waiter-specific annotations and labels.
This change would be two stages:
Add the waiter/cluster label redundantly.
After some reasonable amount of time (i.e., when we're confident that all of the objects without waiter/cluster have been deleted or replaced), remove the waiter-cluster label and switch our queries (e.g., watches) to use the new waiter/cluster label.
The text was updated successfully, but these errors were encountered:
For Kubernetes objects created by Waiter, we should be using the
namespace/property
naming convention for all of our Waiter-specific annotations and labels.This change would be two stages:
waiter/cluster
label redundantly.waiter/cluster
have been deleted or replaced), remove thewaiter-cluster
label and switch our queries (e.g., watches) to use the newwaiter/cluster
label.The text was updated successfully, but these errors were encountered: