Skip to content

Forcing kubectl log to wait when container is creating #1227

Open
@nalepae

Description

What would you like to be added:

When we do kubectl logs <pod> [-f] on a container in creation, we get this error message:

Error from server (BadRequest): container "<container>" in pod "<pod>" is waiting to start: [ContainerCreating, PodInitializing]

In this situation, in general we retry to launch the kubectl logs <pod> [-f] until the container is created.

A nice feature would be to have a the kubectl logs command to block until the container is created, so we run this command only one time.

Why is this needed:
To simplify the life of the user.

Metadata

Assignees

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.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions