aaaaaaa

[neo-liang-sap]

Which cluster is affected?

Cluster Details Dashboard Link: URL

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 normal

[gardener-robot-dev]

@neo-liang-sap Oops, the dashboard link that you have provided (domain garden.canary.k8s.ondemand.com) does not match this repository (domains staging.gardener.cloud.sap, garden.staging.k8s.ondemand.com). Please open the issue at the correct repository. You can invoke the cluster self-diagnosis yourself later with /diag on a separate line in a comment to this issue.

[gardener-robot-dev]

@neo-liang-sap No more than 5 labels permitted, but 21 labels were given.

[gardener-robot-dev]

@neo-liang-sap The issue was assigned to you under author-action. Please unassign yourself when you are done. Thank you.

[gardener-robot-dev]

Ticket was in state author-/owner-action with no further response since 21 days. Closing.