Skip to content

Conversation

@vrutkovs
Copy link
Contributor

@vrutkovs vrutkovs commented Feb 15, 2019

Supersedes #11167

Setup crio 1.12 and ssh bastion in a pod to reach scaled up RHEL nodes

Failing tests:

The bootstrap user should successfully login with password decoded from kubeadmin secret [Suite:openshift/conformance/parallel]
2x [sig-api-machinery] Namespaces [Serial] should ensure that all pods are removed when a namespace is deleted [Conformance] [Suite:openshift/conformance/serial/minimal] [Suite:k8s]

@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 15, 2019
@openshift-ci-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 15, 2019
@vrutkovs vrutkovs force-pushed the devel-40-sshbastion branch 2 times, most recently from 45d20ae to ce23381 Compare February 15, 2019 14:46
@vrutkovs vrutkovs force-pushed the devel-40-sshbastion branch from ce23381 to 6b2893c Compare February 15, 2019 15:04
@vrutkovs
Copy link
Contributor Author

/retest

@openshift-ci-robot openshift-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 15, 2019
backup: yes
section: "crio.image"
option: pause_command
value: ' "/usr/bin/pod"'
Copy link
Contributor

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.

Copy link
Contributor Author

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

Copy link
Contributor

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

@DanyC97
Copy link
Contributor

DanyC97 commented Feb 15, 2019

Vadim, love this ssh bastion pod, is a killer man ! ;)

@vrutkovs
Copy link
Contributor Author

/retest

@mtnbikenc
Copy link
Member

Looks like a few things changed, need to update:
machinesets.machine.openshift.io -> machinesets
openshift-machine-api -> openshift-cluster-api

$ oc get machinesets -o name -n openshift-cluster-api
machineset.cluster.k8s.io/rteague-worker-us-east-2a
machineset.cluster.k8s.io/rteague-worker-us-east-2b
machineset.cluster.k8s.io/rteague-worker-us-east-2c

@mtnbikenc
Copy link
Member

Also:
machines.machine.openshift.io -> machines

@vrutkovs vrutkovs changed the title WIP crio 1.12 and ssh-bastion in a pod crio 1.12 and ssh-bastion in a pod Feb 15, 2019
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 15, 2019
@@ -0,0 +1,17 @@
apiVersion: v1
Copy link
Member

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?

Copy link
Contributor Author

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.

@vrutkovs
Copy link
Contributor Author

/test e2e-aws-scaleup

@mtnbikenc
Copy link
Member

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.

@vrutkovs vrutkovs force-pushed the devel-40-sshbastion branch from aeb24f3 to aca40b5 Compare February 18, 2019 12:08
@vrutkovs vrutkovs force-pushed the devel-40-sshbastion branch 3 times, most recently from 7ba1c1d to a1d622a Compare February 18, 2019 14:34
@vrutkovs vrutkovs force-pushed the devel-40-sshbastion branch from a1d622a to a20829b Compare February 18, 2019 14:34
@vrutkovs
Copy link
Contributor Author

/test e2e-aws-scaleup

8 similar comments
@vrutkovs
Copy link
Contributor Author

/test e2e-aws-scaleup

@vrutkovs
Copy link
Contributor Author

/test e2e-aws-scaleup

@vrutkovs
Copy link
Contributor Author

/test e2e-aws-scaleup

@vrutkovs
Copy link
Contributor Author

/test e2e-aws-scaleup

@vrutkovs
Copy link
Contributor Author

/test e2e-aws-scaleup

@vrutkovs
Copy link
Contributor Author

/test e2e-aws-scaleup

@vrutkovs
Copy link
Contributor Author

/test e2e-aws-scaleup

@vrutkovs
Copy link
Contributor Author

/test e2e-aws-scaleup

@vrutkovs
Copy link
Contributor Author

/retest

@vrutkovs
Copy link
Contributor Author

/test e2e-aws-scaleup

4 similar comments
@vrutkovs
Copy link
Contributor Author

/test e2e-aws-scaleup

@vrutkovs
Copy link
Contributor Author

/test e2e-aws-scaleup

@vrutkovs
Copy link
Contributor Author

/test e2e-aws-scaleup

@vrutkovs
Copy link
Contributor Author

/test e2e-aws-scaleup

@sdodson
Copy link
Member

sdodson commented Feb 20, 2019

/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.

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 20, 2019
@sdodson sdodson merged commit 168f41f into openshift:devel-40 Feb 20, 2019
@openshift-ci-robot
Copy link

[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

Details Needs approval from an approver in each of these files:

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

@openshift-ci-robot
Copy link

@vrutkovs: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/prow/e2e-aws-scaleup a20829b link /test e2e-aws-scaleup

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.

Details

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 understand the commands that are listed here.

@vrutkovs vrutkovs deleted the devel-40-sshbastion branch February 20, 2019 15:52
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. lgtm Indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants