-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Managed NS: update default configuration values #3929
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
Managed NS: update default configuration values #3929
Conversation
saschagrunert
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
7476a6c to
a83e8c9
Compare
Codecov Report
@@ Coverage Diff @@
## master #3929 +/- ##
==========================================
+ Coverage 40.51% 40.70% +0.18%
==========================================
Files 109 109
Lines 8829 8823 -6
==========================================
+ Hits 3577 3591 +14
+ Misses 4927 4903 -24
- Partials 325 329 +4 |
80aaec6 to
646591f
Compare
docs/crio.conf.5.md
Outdated
|
|
||
| **manage_ns_lifecycle**=false | ||
| **manage_ns_lifecycle**=true | ||
| Determines whether we pin and remove namespaces and manage their lifecycle |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know it's pre-existing, but missing ending period.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was the one that wrote the original anyway 😎
set ManageNSLifecycle to true by default remove deprecated --manage-network-ns-lifecycle flag and config entry Signed-off-by: Peter Hunt <[email protected]>
there are situations in which we need to restore a stopped pod. specifically, if the node was rebooted, but the kubelet didn't delete the container, then the pod will be stopped and will need to be garbage collected if we remove the namespaces on a stop call, the sandboxes will fail to restore, and the sandboxes won't appear in the list of pods for the kubelet to clean up Signed-off-by: Peter Hunt <[email protected]>
646591f to
d8615ec
Compare
|
lgtm |
TomSweeneyRedHat
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, mrunalp, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
|
/retest |
|
/test e2e-aws |
|
/retest |
What type of PR is this?
/kind api-change
What this PR does / why we need it:
This PR does three things:
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?