-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
create a hybrid cluster and run the e2e tests on it #8075
create a hybrid cluster and run the e2e tests on it #8075
Conversation
eaba01b
to
d17b7fb
Compare
/retest |
ed8d728
to
a36526a
Compare
@stevekuznetsov PTAL |
|
||
TF_LOG=debug openshift-install --dir="${dir}" create manifests | ||
|
||
cat >> "${dir}/manifests/cluster-network-03-config.yml" << EOF |
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.
I would much rather see you break apart the current install step into a manifest-create and a run-install or something. Whenver we find ourselves copy-pasting in this system we need to be refactoring to make this reusable
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.
updated with the code split into steps
407363e
to
ba96aa9
Compare
@@ -0,0 +1,31 @@ | |||
#!/bin/bash |
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.
I meant -- everyone running the installer should ideally be using the same steps to do so, or we have drift. So this should underpin the IPI install flow, too.
222094e
to
355b05c
Compare
/retest |
355b05c
to
6d03e1a
Compare
/retest |
@JacobTanenbaum: The following tests 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. 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. |
@@ -7,4 +7,4 @@ ref: | |||
cpu: 1000m | |||
memory: 2Gi | |||
documentation: |- | |||
The IPI install step runs the OpenShift Installer in order to bring up an OpenShift cluster, using the provided cluster profile to choose a target IaaS platform. | |||
The IPI install step runs the OpenShift Installer in order to bring up an OpenShift cluster, using the provided cluster profile to choose a target IaaS platform. Anything that needs to be configured using manifests should generate them before this step and put them in the SHARED_DIR with the filename manifest_(manifest_name).yml so that this step can pull in the manifest in. |
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.
@AlexNPavel can we embed HTML here or something? I would love to see a fully-fledged example.
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 could allow markdown and use https://godoc.org/github.com/gomarkdown/markdown/html to convert to html for steps.svc.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JacobTanenbaum, stevekuznetsov The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@JacobTanenbaum: Updated the following 9 configmaps:
In 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. |
…ests' No Terraform involved in creating manifests. Cleans up after d11bca7 (create a hybrid cluster and run the e2e tests on it, 2020-04-01, openshift#8075). Also removes trailing whitespace from the YAML documentation. Also backgrounds the 'create manifests' call and immediately waits for it, so we can gracefully handle TERM as described in 4472ace (ci-operator/templates/openshift/installer: Restore backgrounded 'create cluster', 2019-01-23, openshift#2680).
Use the hybrid OVN step registry introduced in openshift#8075 for the operator's e2e tests. Ran `make jobs` after adding the step registry config.
No description provided.