Labels · gardener-attic/issues-foo

Issue is created because the cluster is both a failed and expired state

We can ignore this

Gardener blocked, user must clean up blocking infrastructure components

Gardener blocked, user must provide credentials with proper permissions (authorization failed)

We do not understand this

Gardener blocked, user must provide valid credentials (authentication failed)

Some resources (on Kubernetes, Gardener or infrastructure side) leaked

We cannot reproduce this

Gardener blocked, user must increase quota/limits

The issue is not on our side but in an upstream project (e.g. k/k)

We will not fix this

Provide feedback