Skip to main content
Question

kubelet  Startup probe failed: tcp

  • January 13, 2026
  • 1 reply
  • 19 views

Forum|alt.badge.img+11

Hi heros,

 

Getting the message below when from a ifsapp-connect pod:

 

Events:
  Type     Reason     Age    From     Message
  ----     ------     ----   ----     -------
  Warning  Unhealthy  4m55s  kubelet  Startup probe failed: tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN
--connect container not ready--
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\r100  2618  100  2532  100    86   125k   4354 --:--:-- --:--:-- --:--:--  134k
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\r100   886    0   849  100    37  12332    537 --:--:-- --:--:-- --:--:-- 13029
  Warning  Unhealthy  3m55s  kubelet  Startup probe failed: tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN
--connect container not ready--

 

Any idea?

Client running : 24.2.7

 

Thank,

 

Gianni Neves

1 reply

Forum|alt.badge.img+11
  • Author
  • Hero (Customer)
  • January 13, 2026

Looking into my IFSAPP-IAM, I am getting this message: Startup probe failed: IFSIAM container not ready, but it started because I have 2/2.

Is it normal?