Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Stale image in "Configure Liveness, Readiness and Startup Probes" #49406

Open
harshitsahu2311 opened this issue Jan 13, 2025 · 4 comments
Open

Stale image in "Configure Liveness, Readiness and Startup Probes" #49406

harshitsahu2311 opened this issue Jan 13, 2025 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. language/en Issues or PRs related to English language triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@harshitsahu2311
Copy link

In this document the yaml file for liveness probe using registry.k8s.io/busybox is showing depricated, but as I used busybox official image it is running as expected outputs.
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jan 13, 2025
@sftim
Copy link
Contributor

sftim commented Jan 13, 2025

/retitle Stale image in "Configure Liveness, Readiness and Startup Probes"
/language en

@k8s-ci-robot k8s-ci-robot changed the title Configure Liveness, Readiness and Startup Probes Stale image in "Configure Liveness, Readiness and Startup Probes" Jan 13, 2025
@k8s-ci-robot k8s-ci-robot added the language/en Issues or PRs related to English language label Jan 13, 2025
@sftim
Copy link
Contributor

sftim commented Jan 13, 2025

I think this issue is about https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/

@sftim
Copy link
Contributor

sftim commented Jan 13, 2025

Assuming that we stick with Busybox:

  • we should pin to a specific busybox image version
  • we should make sure to use a current container image for Busybox (doesn't have to come from registry.k8s.io)

@sftim
Copy link
Contributor

sftim commented Jan 13, 2025

/kind bug
/triage accepted

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. language/en Issues or PRs related to English language triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@k8s-ci-robot @sftim @harshitsahu2311