Skip to content

test issue #110

@neo-liang-sap

Description

@neo-liang-sap

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

Metadata

Metadata

Assignees

Labels

lifecycle/staleNobody worked on this for 6 months (will further age)notification/pager-dutyNo notification neededpriority/blockerNeeds to be resolved now, because it breaks the servicestatus/in-progressIssue is in progress/worktopology/shootAffects Shoot clusters

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions