I have a fresh install, talos linux, with version 38.0 is in a crash loop, however 37.1 works just fine. I have tried removing any resource constraints cpu/mem, and giving privileged security admission. changing to log level debug doesn't show much more. Please let me know what else is needed.
Thanks
❯ kubectl describe pod -n flux-system image-automation-controller-fb6c9df74-dm8hj
Name: image-automation-controller-fb6c9df74-dm8hj
Namespace: flux-system
Priority: 0
Service Account: image-automation-controller
Node: node01/192.168.1.41
Start Time: Fri, 20 Sep 2024 04:07:40 +0000
Labels: app=image-automation-controller
pod-template-hash=fb6c9df74
Annotations: prometheus.io/port: 8080
prometheus.io/scrape: true
Status: Running
IP: 10.69.0.59
IPs:
IP: 10.69.0.59
Controlled By: ReplicaSet/image-automation-controller-fb6c9df74
Containers:
manager:
Container ID: containerd://6075fae919b8efa9c95aa3b52b6786f26840f0cbb36b5c23aca444e8ee09f368
Image: ghcr.io/fluxcd/image-automation-controller:v0.38.0
Image ID: ghcr.io/fluxcd/image-automation-controller@sha256:ab5097213194f3cd9f0e68d8a937d94c4fc7e821f6544453211e94815b282aa2
Ports: 8080/TCP, 9440/TCP
Host Ports: 0/TCP, 0/TCP
SeccompProfile: RuntimeDefault
Args:
--events-addr=http://notification-controller.flux-system.svc.cluster.local./
--watch-all-namespaces=true
--log-level=info
--log-encoding=json
--enable-leader-election
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 2
Started: Fri, 20 Sep 2024 04:13:26 +0000
Finished: Fri, 20 Sep 2024 04:13:26 +0000
Ready: False
Restart Count: 6
Limits:
cpu: 1
memory: 1Gi
Requests:
cpu: 100m
memory: 64Mi
Liveness: http-get http://:healthz/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
Readiness: http-get http://:healthz/readyz delay=0s timeout=1s period=10s #success=1 #failure=3
Environment:
RUNTIME_NAMESPACE: flux-system (v1:metadata.namespace)
GOMAXPROCS: 1 (limits.cpu)
GOMEMLIMIT: 1073741824 (limits.memory)
Mounts:
/tmp from temp (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-s7fxk (ro)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
temp:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
SizeLimit: <unset>
kube-api-access-s7fxk:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: Burstable
Node-Selectors: kubernetes.io/os=linux
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 5m56s default-scheduler Successfully assigned flux-system/image-automation-controller-fb6c9df74-dm8hj to node01
Normal Pulled 4m27s (x5 over 5m55s) kubelet Container image "ghcr.io/fluxcd/image-automation-controller:v0.38.0" already present on machine
Normal Created 4m27s (x5 over 5m55s) kubelet Created container manager
Normal Started 4m27s (x5 over 5m55s) kubelet Started container manager
Warning BackOff 46s (x26 over 5m54s) kubelet Back-off restarting failed container manager in pod image-automation-controller-fb6c9df74-dm8hj_flux-system(4cd869f6-a2db-4b86-a0c8-05069d324d62)
Hello,
I have a fresh install, talos linux, with version 38.0 is in a crash loop, however 37.1 works just fine. I have tried removing any resource constraints cpu/mem, and giving privileged security admission. changing to log level debug doesn't show much more. Please let me know what else is needed.
Thanks