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

Procedure for tenants to collect core dumps of failing containers #82530

Open
mcandre opened this issue Sep 10, 2019 · 6 comments

Comments

@mcandre
Copy link

commented Sep 10, 2019

What would you like to be added:

An automated, straightforward procedure for cluster tenants to collect core dumps of failing containers.

Why is this needed:

So that segmentation faults can be diagnosed at scale without exposing unnecessary privileges to k8ts tenants.

@mcandre

This comment has been minimized.

Copy link
Author

commented Sep 10, 2019

@kubernetes/sig-community-discussion

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

commented Sep 10, 2019

@mcandre: The label(s) sig/feature-requests cannot be appled. These labels are supported: api-review, community/discussion, community/maintenance, community/question, cuj/build-train-deploy, cuj/multi-user, platform/aws, platform/azure, platform/gcp, platform/minikube, platform/other

In response to this:

/sig feature-requests

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

This comment has been minimized.

Copy link
Contributor

commented Sep 10, 2019

@mcandre: The label(s) sig/community-discussion cannot be appled. These labels are supported: api-review, community/discussion, community/maintenance, community/question, cuj/build-train-deploy, cuj/multi-user, platform/aws, platform/azure, platform/gcp, platform/minikube, platform/other

In response to this:

/sig community-discussion

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

This comment has been minimized.

Copy link
Contributor

commented Sep 10, 2019

@mcandre: The label(s) sig/community/discussion cannot be appled. These labels are supported: api-review, community/discussion, community/maintenance, community/question, cuj/build-train-deploy, cuj/multi-user, platform/aws, platform/azure, platform/gcp, platform/minikube, platform/other

In response to this:

/sig community/discussion

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.

@mcandre

This comment has been minimized.

Copy link
Author

commented Sep 10, 2019

You are a stupid bot.

@neolit123

This comment has been minimized.

Copy link
Member

commented Sep 11, 2019

/sig node auth
please try to provide more detail in the issue description.
to get attention on this topic try posting a message in the k8s slack channel: #wg-multitenancy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.