Bug 1825339: [4.4] crio: manage ns lifecycle#1871
Bug 1825339: [4.4] crio: manage ns lifecycle#1871openshift-merge-robot merged 1 commit intoopenshift:release-4.4from
Conversation
change the entry in crio.conf template to manage ns lifecycle As it is more secure and gives cri-o more control of namespace lifecycle. Also change the outdated config name value Signed-off-by: Peter Hunt <pehunt@redhat.com>
|
@haircommander: This pull request references Bugzilla bug 1825339, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 6 validation(s) were run on this bug
DetailsIn response to this:
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. |
|
/retest |
1 similar comment
|
/retest |
|
/skip |
|
/assign @umohnani8 @mtrmac |
|
/skip |
|
/test e2e-metal-ipi |
|
we may need some variation of openshift/cluster-network-operator#645 I think we should wait till next week on this |
|
Holding until next week... Feel free to remove. /hold |
|
For sure we need openshift/cluster-network-operator#684 to get in before this. |
|
This got already merged: openshift/cluster-network-operator#684 |
|
excellent! |
|
@haircommander: This pull request references Bugzilla bug 1825339. The bug has been updated to no longer refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
|
excellent! |
|
@haircommander: This pull request references Bugzilla bug 1825339, which is invalid:
Comment DetailsIn response to this:
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. |
|
I confused myself, this was not meant to be closed |
|
/bugzilla refresh |
|
@haircommander: This pull request references Bugzilla bug 1825339, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 6 validation(s) were run on this bug
DetailsIn response to this:
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. |
|
/test e2e-aws |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, kikisdeliveryservice, umohnani8 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 |
|
/hold cancel the dependent PRs have all merged |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/skip |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@haircommander: All pull requests linked via external trackers have merged: openshift/machine-config-operator#1871. Bugzilla bug 1825339 has been moved to the MODIFIED state. DetailsIn response to this:
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. |
- What I did
change the entry in crio.conf template to manage ns lifecycle
As it is more secure and gives cri-o more control of namespace lifecycle. Also change the outdated config name value
backport of #1689
- How to verify it
- Description for the changelog
CRI-O now manages namespace lifecycle