Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Failed to undeploy cluster backup components" on new clusters #13181

Closed
embik opened this issue Mar 15, 2024 · 3 comments · Fixed by #13403
Closed

"Failed to undeploy cluster backup components" on new clusters #13181

embik opened this issue Mar 15, 2024 · 3 comments · Fixed by #13403
Labels
customer-request kind/bug Categorizes issue or PR as related to a bug. sig/app-management Denotes a PR or issue as being assigned to SIG App Management.

Comments

@embik
Copy link
Member

embik commented Mar 15, 2024

What happened?

When creating a new user cluster in KKP v2.25.0-rc.0, the very early phases of cluster creation often see events on the cluster regarding cluster backup components:

failed to undeploy cluster backup user-cluster components: failed to undeploy cluster backup user-cluster resources: failed to delete cluster backup user-cluster resource: failed to get API group resources: unable to retrieve the complete list of server APIs: apps/v1: Get "https://apiserver-external.cluster-a5pvzhh49r.svc.cluster.local./apis/apps/v1": dial tcp 10.240.27.81:443: connect: operation not permitted

failed to undeploy cluster backup user-cluster components: failed to get user cluster client: Secret "internal-admin-kubeconfig" not found

This doesn't seem to have any impact and vanishes as soon as more components of the user cluster are up, but I feel like this code path should be more vigilant in checking the cluster status before trying to get clients.

No cluster backup is intended to be used.

Expected behavior

These warnings do not show up.

How to reproduce the issue?

  • Create new user clusters on KKP v2.25.0-rc.0

How is your environment configured?

  • KKP version: v2.25.0-rc.0
  • Shared or separate master/seed clusters?: shared

Provide your KKP manifest here (if applicable)

# paste manifest here

What cloud provider are you running on?

N/A

What operating system are you running in your user cluster?

N/A

Additional information

@embik embik added the kind/bug Categorizes issue or PR as related to a bug. label Mar 15, 2024
@SamuAlfageme
Copy link

I'm still seeing reproducing this on a freshly deployed KKP v2.25.4, even when the experimental user-cluster feature flag is not enabled.

@archups
Copy link
Contributor

archups commented May 22, 2024

/customer-request
Customer is affected by this issue.

@csengerszabo
Copy link
Contributor

/label sig/app-management

@kubermatic-bot kubermatic-bot added the sig/app-management Denotes a PR or issue as being assigned to SIG App Management. label May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-request kind/bug Categorizes issue or PR as related to a bug. sig/app-management Denotes a PR or issue as being assigned to SIG App Management.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants