Skip to content
This repository has been archived by the owner on Apr 25, 2023. It is now read-only.

Clusters are not getting joined in Kubernetes V1.24 and above using kubefedctl join #1528

Closed
shivanisinghnitp opened this issue Nov 23, 2022 · 5 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@shivanisinghnitp
Copy link

shivanisinghnitp commented Nov 23, 2022

What happened: When I try joining clusters using kubefedctl join, it throws an error and the clusters aren't joined.
Screenshot 2022-11-23 at 9 38 30 AM
What you expected to happen: The clusters should join

How to reproduce it (as minimally and precisely as possible):
Screenshot 2022-11-23 at 9 30 01 AM
Screenshot 2022-11-23 at 9 31 39 AM

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version) - 1.25
  • KubeFed version - latest
  • Scope of installation (namespaced or cluster)
  • Others

/kind bug

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Nov 23, 2022
@ebiiim
Copy link

ebiiim commented Nov 24, 2022

I had the same issue and found that kubefedctl v0.10.0 might work.

Might be related to #1515.

@lpc-v
Copy link

lpc-v commented Jan 12, 2023

Have you met a problem: cluster 2 is not ready

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 12, 2023
@mrbobbytables
Copy link

Project is to be archived - closing all issues and PRs

see kubernetes/org#4122 and https://groups.google.com/d/msgid/kubernetes-sig-multicluster/9f8d81d1-07d1-4985-a7bf-d76197deb971n%40googlegroups.com

for details

/close

@k8s-ci-robot
Copy link
Contributor

@mrbobbytables: Closing this issue.

In response to this:

Project is to be archived - closing all issues and PRs

see kubernetes/org#4122 and https://groups.google.com/d/msgid/kubernetes-sig-multicluster/9f8d81d1-07d1-4985-a7bf-d76197deb971n%40googlegroups.com

for details

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

6 participants