Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@haircommander
Copy link
Member

What type of PR is this?

/kind api-change

What this PR does / why we need it:

This PR does three things:

  • set managed ns lifecycle to true by default
  • finishes deprecation of ManageNetworkNSLifecycle flag and config value (set as deprecated in 4.4)
  • fixes a small test inconsistency with how we restore a managed ns pod. Before, we removed the managed namespaces on sandbox stop. however, this caused crio to fail to restore the pod (as it was looking for the managed ns which didn't exist). instead, only remove the namespaces on sandbox remove

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

CRI-O now manages namespace lifecycles by default (manage_ns_lifecycle = true). The config option manage_network_ns_lifecycle has also been fully deprecated

@openshift-ci-robot openshift-ci-robot added kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Jul 6, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 6, 2020
Copy link
Member

@saschagrunert saschagrunert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@codecov
Copy link

codecov bot commented Jul 7, 2020

Codecov Report

Merging #3929 into master will increase coverage by 0.18%.
The diff coverage is 100.00%.

@@            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     

@haircommander haircommander force-pushed the manage-ns-default branch 3 times, most recently from 80aaec6 to 646591f Compare July 11, 2020 01:15

**manage_ns_lifecycle**=false
**manage_ns_lifecycle**=true
Determines whether we pin and remove namespaces and manage their lifecycle
Copy link
Contributor

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.

Copy link
Member Author

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]>
@harche
Copy link
Contributor

harche commented Jul 16, 2020

lgtm

Copy link
Contributor

@TomSweeneyRedHat TomSweeneyRedHat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@openshift-ci-robot
Copy link

[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

Details Needs approval from an approver in each of these files:
  • OWNERS [haircommander,mrunalp,saschagrunert]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mrunalp
Copy link
Member

mrunalp commented Jul 16, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 16, 2020
@haircommander
Copy link
Member Author

/retest

@haircommander
Copy link
Member Author

/test e2e-aws

@haircommander
Copy link
Member Author

/retest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants