-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Labels
lifecycle/staleNobody worked on this for 6 months (will further age)Nobody worked on this for 6 months (will further age)notification/pager-dutyNo notification neededNo notification neededpriority/blockerNeeds to be resolved now, because it breaks the serviceNeeds to be resolved now, because it breaks the servicestatus/in-progressIssue is in progress/workIssue is in progress/worktopology/shootAffects Shoot clustersAffects Shoot clusters
Description
Which cluster is affected?
Cluster Details Dashboard Link: https://dashboard.garden.dev.k8s.ondemand.com/namespace/garden-sretestneo/shoots/sre-g-test/
What happened?
What you expected to happen?
When did it happen or started to happen?
Absolute:
Relative:
How would we reproduce it (concisely and precisely)?
Anything else we need to know?
Help us categorise this issue for faster resolution:
/area audit-logging auto-scaling backup certification control-plane cost delivery disaster-recovery documentation high-availability logging metering monitoring networking os performance quality security storage usability user-management
/component gardener dashboard documentation
/kind bug regression post-mortem
/os garden-linux suse-chost
/platform alicloud aws azure gcp converged-cloud
/priority critical
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
lifecycle/staleNobody worked on this for 6 months (will further age)Nobody worked on this for 6 months (will further age)notification/pager-dutyNo notification neededNo notification neededpriority/blockerNeeds to be resolved now, because it breaks the serviceNeeds to be resolved now, because it breaks the servicestatus/in-progressIssue is in progress/workIssue is in progress/worktopology/shootAffects Shoot clustersAffects Shoot clusters