-
Notifications
You must be signed in to change notification settings - Fork 19
Open
Description
-
Hub agent fails to start because the applied Deployment object gets
--log_file_max_size=flag with no value. -
Member agent fails to start because of error:
member-agent-5fd8d4d87-cvssj member-agent E1020 17:43:29.904455 1 workspace/main.go:249] "Failed to retrieve token file from the path %s" err="stat /config/token: no such file or directory" /config/token="(MISSING)"
member-agent-5fd8d4d87-cvssj member-agent panic: runtime error: invalid memory address or nil pointer dereference
member-agent-5fd8d4d87-cvssj member-agent [signal SIGSEGV: segmentation violation code=0x1 addr=0x1d0 pc=0x1548328]
The same thing works in kind 1.23.0 image but not 1.34.0, maybe the ServiceAccount automount token behavior change has broken the tutorial.
In the meanwhile, membercluster object exists but doesn't ready-up:
apiVersion: cluster.kubernetes-fleet.io/v1
kind: MemberCluster
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"cluster.kubernetes-fleet.io/v1beta1","kind":"MemberCluster","metadata":{"annotations":{},"name":"spoke"},"spec":{"heartbeatPeriodSeconds":15,"identity":{"apiGroup":"","kind":"ServiceAccount","name":"spoke-hub-cluster-access","namespace":"fleet-system"}}}
creationTimestamp: "2025-10-20T17:39:20Z"
finalizers:
- kubernetes-fleet.io/membercluster-finalizer
- kubernetes-fleet.io/cluster-profile-cleanup
generation: 3
name: spoke
resourceVersion: "212612"
uid: 6c6406b4-1ab5-47e1-8842-915338410a80
spec:
heartbeatPeriodSeconds: 15
identity:
apiGroup: ""
kind: ServiceAccount
name: spoke-hub-cluster-access
namespace: fleet-system
status:
conditions:
- lastTransitionTime: "2025-10-20T17:39:20Z"
message: Member cluster is ready to join the fleet
observedGeneration: 3
reason: MemberClusterReadyToJoin
status: "True"
type: ReadyToJoin
- lastTransitionTime: "2025-10-20T17:39:20Z"
message: Member cluster spoke has not reported all the expected agents, expected
1, got 0
observedGeneration: 3
reason: MemberClusterJoinStateUnknown
status: Unknown
type: Joined
resourceUsage: {}Metadata
Metadata
Assignees
Labels
No labels