-
Notifications
You must be signed in to change notification settings - Fork 2.3k
crio 1.12 and ssh-bastion in a pod #11203
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
Conversation
45d20ae to
ce23381
Compare
ce23381 to
6b2893c
Compare
|
/retest |
| backup: yes | ||
| section: "crio.image" | ||
| option: pause_command | ||
| value: ' "/usr/bin/pod"' |
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.
you didn't like the template ?
imo a template would give you a much better flexibility in the long run when things will get much more stable and you will realize you want to do some tuning.
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.
We don't directly control the crio versions, unlike docker, so its best to modify just the required parts
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.
right, i was coming from the angle where later the default CRI-O settings won't satisfy the needs of BYO .. i guess we can cross that bridge when we come to it
|
Vadim, love this ssh bastion pod, is a killer man ! ;) |
|
/retest |
|
Looks like a few things changed, need to update: |
|
Also: |
| @@ -0,0 +1,17 @@ | |||
| apiVersion: v1 | |||
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.
If there's any chance we'll drop more stuff in here should we name them 01_ssh_service.yml, 02_ssh_serviceaccount.yml, etc?
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.
Right, oc apply applies files in alphabetical order, so first the namespace has to be created, then a service etc.
|
/test e2e-aws-scaleup |
|
My two comments above about needing to change machines and machinesets was due to the fact I was using the 0.12 installer. After building the installer from master I didn't have those issues. |
aeb24f3 to
aca40b5
Compare
…beconfig_path is set
7ba1c1d to
a1d622a
Compare
a1d622a to
a20829b
Compare
|
/test e2e-aws-scaleup |
8 similar comments
|
/test e2e-aws-scaleup |
|
/test e2e-aws-scaleup |
|
/test e2e-aws-scaleup |
|
/test e2e-aws-scaleup |
|
/test e2e-aws-scaleup |
|
/test e2e-aws-scaleup |
|
/test e2e-aws-scaleup |
|
/test e2e-aws-scaleup |
|
/retest |
|
/test e2e-aws-scaleup |
4 similar comments
|
/test e2e-aws-scaleup |
|
/test e2e-aws-scaleup |
|
/test e2e-aws-scaleup |
|
/test e2e-aws-scaleup |
|
/lgtm As a team we feel that this code is generally working as intended, however we're running into persistent e2e test failures that we'll need to address with other teams. Merging as is. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sdodson, vrutkovs 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 |
|
@vrutkovs: 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. |
Supersedes #11167
Setup crio 1.12 and ssh bastion in a pod to reach scaled up RHEL nodes