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

Issue with k8s.io/docs/tasks/administer-cluster/static-pod/ #12467

Closed
1 of 2 tasks
AlexDiamanti opened this issue Jan 31, 2019 · 8 comments
Closed
1 of 2 tasks

Issue with k8s.io/docs/tasks/administer-cluster/static-pod/ #12467

AlexDiamanti opened this issue Jan 31, 2019 · 8 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@AlexDiamanti
Copy link

Needed more info in the docs.

This is a...

  • Feature Request
  • Bug Report

Problem:
What happens and how it is different when you create a pod from kubectl create -f POD_FILE.yaml

It's not static. Seems like it's different from pods controlled by the services in terms of how psp gets applied.

Proposed Solution:

Page to Update:
https://kubernetes.io/...

@sftim
Copy link
Contributor

sftim commented Feb 16, 2019

If this page explained that static pods would be created regardless of all admission controllers (and gave PodSecurityPolicy as an example), would that resolve this issue?

@AlexDiamanti
Copy link
Author

My understanding that kubelet also needs to restart static pod if somehow was an issue with the scheduling (node was not ready, psp was not allowing, etc). It's just could be broken in the current versions according to that: kubernetes/kubernetes#73309

Would be nice to have more details there...

@sftim
Copy link
Contributor

sftim commented Feb 19, 2019

Would it make sense to log an issue that calls for more detail, and hyperlink to the page with the extra detail once it exists?

@AlexDiamanti
Copy link
Author

Sure

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 20, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 19, 2019
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants