templates: move recycler pod out of kubelet manifests directory#2238
Conversation
|
also @haircommander |
|
Indeed the old file still needs to be there |
e727f58 to
400618a
Compare
400618a to
9790e1d
Compare
|
/retest |
|
/retest |
|
OK I see, and it's then configured by the other pod. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgwalters, JAORMX, sjenning 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 |
|
It'd be good I think to change https://github.com/openshift/cluster-kube-controller-manager-operator to detect the path dynamically - that would avoid a version interlock between the these two codebases and make backporting easier. (i.e. mount Also this file would be another good one to add to this #2232 (comment) |
|
/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. |
|
@sjenning: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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 understand the commands that are listed here. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
xref https://bugzilla.redhat.com/show_bug.cgi?id=1896226
This is the first step in resolving a bug introduced by #1687 and openshift/cluster-kube-controller-manager-operator#405
/etc/kubernetes/manifestsis the kubelet's static pod manifests directory. The kubelet will try to start pods defined in this location as static pods. The recycler pod is not a static pod and the kubelet continuously fails to start it.The solution is to move the recycler pod manifests to a different directory.
The fix is a 3-step process (as I see it):
@runcom @sttts @rphillips