PS C:\Work\Claude\medplum-private\charts> kubectl describe pod -n medplum medplum-server-6d76766c49-6cgv9 Name: medplum-server-6d76766c49-6cgv9 Namespace: medplum Priority: 0 Service Account: medplum-server Node: gk3-medplum-gke-pool-2-025fdb95-pr4c/10.0.0.3 Start Time: Fri, 31 Jan 2025 12:23:31 -0600 Labels: app.kubernetes.io/instance=medplum-server app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=medplum app.kubernetes.io/version=3.2.27 helm.sh/chart=medplum-0.1.0 pod-template-hash=6d76766c49 Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.100.0.22 IPs: IP: 10.100.0.22 Controlled By: ReplicaSet/medplum-server-6d76766c49 Containers: medplum: Container ID: containerd://7d67af839e0df3ad367fda730f8e201d89a0e62de48558dc79c0af41d3d1500d Image: medplum/medplum-server:latest Image ID: docker.io/medplum/medplum-server@sha256:95bdb14ae75a232917134e9368f448d87c5830e0e82d5652a0b93f79c24f6d3d Port: 8103/TCP Host Port: 0/TCP Args: gcp:composite-store-387221:config-secret State: Waiting Reason: CrashLoopBackOff Last State: Terminated Reason: Error Exit Code: 1 Started: Fri, 31 Jan 2025 12:23:43 -0600 Finished: Fri, 31 Jan 2025 12:23:52 -0600 Ready: False Restart Count: 1 Limits: ephemeral-storage: 1Gi memory: 2Gi Requests: cpu: 154m ephemeral-storage: 1Gi memory: 1Gi Liveness: http-get http://:8103/healthcheck delay=0s timeout=1s period=10s #success=1 #failure=3 Readiness: http-get http://:8103/healthcheck delay=0s timeout=1s period=10s #success=1 #failure=3 Environment: Mounts: /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-k8t85 (ro) Readiness Gates: Type Status cloud.google.com/load-balancer-neg-ready True Conditions: Type Status cloud.google.com/load-balancer-neg-ready True PodReadyToStartContainers True Initialized True Ready False ContainersReady False PodScheduled True Volumes: kube-api-access-k8t85: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: DownwardAPI: true QoS Class: Burstable Node-Selectors: Tolerations: kubernetes.io/arch=amd64:NoSchedule 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 LoadBalancerNegNotReady 34s neg-readiness-reflector Unable to determine the pod's node name. Normal Scheduled 34s gke.io/optimize-utilization-scheduler Successfully assigned medplum/medplum-server-6d76766c49-6cgv9 to gk3-medplum-gke-pool-2-025fdb95-pr4c Normal LoadBalancerNegNotReady 34s neg-readiness-reflector Waiting for pod to become healthy in at least one of the NEG(s): [k8s1-f5e87c60-medplum-medplum-server-service-80-5dd95b33] Normal LoadBalancerNegWithoutHealthCheck 27s neg-readiness-reflector Pod is in NEG "Key{\"k8s1-f5e87c60-medplum-medplum-server-service-80-5dd95b33\", zone: \"us-central1-b\"}". NEG is not attached to any BackendService with health checking. Marking condition "cloud.google.com/load-balancer-neg-ready" to True. Normal Pulled 22s (x2 over 33s) kubelet Container image "medplum/medplum-server:latest" already present on machine Normal Created 22s (x2 over 33s) kubelet Created container medplum Normal Started 22s (x2 over 33s) kubelet Started container medplum Warning Unhealthy 14s (x5 over 32s) kubelet Readiness probe failed: Get "http://10.100.0.22:8103/healthcheck": dial tcp 10.100.0.22:8103: connect: connection refused Warning Unhealthy 14s (x2 over 24s) kubelet Liveness probe failed: Get "http://10.100.0.22:8103/healthcheck": dial tcp 10.100.0.22:8103: connect: connection refused Warning BackOff 4s (x2 over 12s) kubelet Back-off restarting failed container medplum in pod medplum-server-6d76766c49-6cgv9_medplum(1ca79cab-93a9-474e-8ef4-497bba6faed8)PS C:\Work\Claude\medplum-private\charts>