Skip to content

Container name not showed in the probe event message #129299

@astraw99

Description

@astraw99

What would you like to be added?

Add container name Container abc in the probe event message, like:

Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  18m                   default-scheduler  Successfully assigned xxx/xxx-controller-manager-7c8fcd5fff-4fprb to cloud-dev
  Normal   Pulling    20m                   kubelet            Pulling image "xxx/xxx/xxx:v0.0.1"
  Normal   Pulled     20m                   kubelet            Successfully pulled image "xxx/xxx/xxx-controller:v0.0.1"
  Normal   Started    20m                   kubelet            Started container manager
  Normal   Created    20m                   kubelet            Created container manager
  Normal   Created    19m (x4 over 20m)     kubelet            Created container kube-rbac-proxy
  Normal   Started    19m (x4 over 20m)     kubelet            Started container kube-rbac-proxy
  ...
  Warning  Unhealthy  2m58s (x31 over 10m)  kubelet            [Container abc] Readiness probe failed: HTTP probe failed with statuscode: 500

Why is this needed?

When there are multiple containers in a pod, we use kubectl describe po xxx to show the events,
it is not showing the failed container name, but it is useful and needed.

Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  18m                   default-scheduler  Successfully assigned xxx/xxx-controller-manager-7c8fcd5fff-4fprb to cloud-dev
  Normal   Pulling    20m                   kubelet            Pulling image "xxx/xxx/xxx:v0.0.1"
  Normal   Pulled     20m                   kubelet            Successfully pulled image "xxx/xxx/xxx-controller:v0.0.1"
  Normal   Started    20m                   kubelet            Started container manager
  Normal   Created    20m                   kubelet            Created container manager
  Normal   Created    19m (x4 over 20m)     kubelet            Created container kube-rbac-proxy
  Normal   Started    19m (x4 over 20m)     kubelet            Started container kube-rbac-proxy
  ...
  Warning  Unhealthy  2m58s (x31 over 10m)  kubelet            Readiness probe failed: HTTP probe failed with statuscode: 500

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.sig/cliCategorizes an issue or PR as relevant to SIG CLI.

    Type

    No type

    Projects

    Status

    In Progress

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions