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.

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

Container Health check set #99692

Closed
HarshitaJha opened this issue Mar 3, 2021 · 4 comments
Closed

Container Health check set #99692

HarshitaJha opened this issue Mar 3, 2021 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@HarshitaJha
Copy link

HarshitaJha commented Mar 3, 2021

This is a question, not an issue.
We are using docker benchmark on our K8s cluster and checking if our containers are compliant by CIS standards. One of the docker benchmarks says that all containers should have the docker healthcheck instruction so that the status of the container, whether healthy (ready for use) or not shows up in the docker inspect command. I was wondering if you could enlighten me if there there is any Kubernetes parameter which can over-write the docker healthcheck and show the health status of the container under docker inspect?
/sig Security

@HarshitaJha HarshitaJha added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 3, 2021
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Mar 3, 2021
@k8s-ci-robot
Copy link
Contributor

@HarshitaJha: There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

  • /sig <group-name>
  • /wg <group-name>
  • /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Mar 3, 2021
@k8s-ci-robot
Copy link
Contributor

@HarshitaJha: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@heqg
Copy link
Contributor

heqg commented Mar 4, 2021

So far, I have not found any parameters that can be overwritten, but there are two prs have been submitted in the community, so the docker health check will no longer take effect in the kubenetes cluster.

for:service pods
#50796

for: sanbox pods
#98552
#98497

I hope it is helpful.

@HarshitaJha
Copy link
Author

Thank you @heqg , this was helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

3 participants