Closed luolanzone closed 1 year ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
same behavior using kubefed master commit a402d2e2750dcc3c094a29a79d8bff53b28fe15d with kind cluster image version from scripts/create-clusters.sh kindest/node:v1.21.1@sha256:69860bda5563ac81e3c0057d654b5253219618a22ec3a346306239bba8cfa1a6 under ubuntu 22.04
At the end of make deploy.kind
:
I0720 15:00:44.911115 274012 join.go:934] Created secret in host cluster named: kind-kind-67dmq
I0720 15:00:44.920646 274012 join.go:299] Created federated cluster resource
But the cluster is not ready:
kubectl -n kube-federation-system get kubefedcluster -o yaml
apiVersion: v1
items:
- apiVersion: core.kubefed.io/v1beta1
kind: KubeFedCluster
metadata:
creationTimestamp: "2022-07-20T13:00:44Z"
generation: 1
managedFields:
- apiVersion: core.kubefed.io/v1beta1
fieldsType: FieldsV1
fieldsV1:
f:spec:
.: {}
f:apiEndpoint: {}
f:caBundle: {}
f:proxyURL: {}
f:secretRef:
.: {}
f:name: {}
manager: kubefedctl
operation: Update
time: "2022-07-20T13:00:44Z"
- apiVersion: core.kubefed.io/v1beta1
fieldsType: FieldsV1
fieldsV1:
f:status:
.: {}
f:conditions: {}
manager: controller-manager
operation: Update
time: "2022-07-20T13:00:45Z"
name: kind-kind
namespace: kube-federation-system
resourceVersion: "1499"
uid: 4a90cc49-ac0a-42d2-8669-51be1c494452
spec:
apiEndpoint: https://127.0.0.1:36671
caBundle: **** removed manually ***
proxyURL: ""
secretRef:
name: kind-kind-67dmq
status:
conditions:
- lastProbeTime: "2022-07-20T13:04:12Z"
lastTransitionTime: "2022-07-20T13:01:02Z"
message: 'cluster is not reachable: Get "https://127.0.0.1:36671/healthz?timeout=3s":
dial tcp 127.0.0.1:36671: connect: connection refused'
reason: ClusterNotReachable
status: "True"
type: Offline
kind: List
metadata:
resourceVersion: ""
selfLink: ""
The cluster seems fine:
kubectl cluster-info
Kubernetes master is running at https://127.0.0.1:36671
CoreDNS is running at https://127.0.0.1:36671/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
127.0.0.1:36671: connect: connection refused
seems to be the root cause
/assign
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Project is to be archived - closing all issues and PRs
see https://github.com/kubernetes/org/issues/4122 and https://groups.google.com/d/msgid/kubernetes-sig-multicluster/9f8d81d1-07d1-4985-a7bf-d76197deb971n%40googlegroups.com
for details
/close
@mrbobbytables: Closing this issue.
What happened:
I was following the quickstart in Readme file to set up kubefed, then I tried the last step
kubectl -n federate-me describe federatedconfigmap my-cm
to check the status, it showsCheckClusters
. thekind
cluster which is joined by default is not ready. Only after I tried to do the patch which is provided infix-joined-kind-clusters.sh
, it can be ready.What you expected to happen: The cluster should be ready by default without patch according to the Readme, but now it requires patch, maybe need to update doc and
fix-joined-kind-clusters.sh
to do the patch in linux as well.How to reproduce it (as minimally and precisely as possible):
Follow the steps in Readme.
Anything else we need to know?:
Environment:
OS: Linux 4.15.0-162-generic #170-Ubuntu SMP Mon Oct 18 11:38:05 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Kind: v0.11.1 go1.16.4 linux/amd64
kubectl version
)/kind bug