[wip] Fix wget to use TLS1.2 #70
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ravisantoshgudimetla 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 |
openshift-ci-robot
added
the
approved
openshift-ci-robot
added
the
do-not-merge/work-in-progress
|
/test e2e-operator |
|
@ravisantoshgudimetla: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
|
Looks like this should have fixed our problems. So closing this PR for now. Let's come back and look at it when MCO team changes the MCS endpoint to use TLS1.3 only |
[wmcb] Rename "run" command to "configure-kubelet"
...the README and the go file. This was missed in PR openshift#70.
- Replace "run" with "initialize-kubelet" that was introduced in openshift#70 - Introduce a Makefile endpoint that builds a Windows binary that will run the e2e tests on a prepared Windows node - Update the README to reflect the new e2e test workflow
2 participants
Test PR to see if this change will help in CI passing consistently.