-
Notifications
You must be signed in to change notification settings - Fork 39
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
adds prow job to install nephio components on kubeadm cluster #297
Conversation
/test e2e-kubeadm-fedora-34 |
0ea00b7
to
0c37574
Compare
/test e2e-kubeadm-ubuntu-jammy |
/test e2e-kubeadm-ubuntu-jammy |
/test e2e-kubeadm-fedora-34 |
/test e2e-kubeadm-ubuntu-jammy |
1 similar comment
/test e2e-kubeadm-ubuntu-jammy |
@vjayaramrh Didn't we decide to bump the fedora version to 40 instead of 34 after R3? |
Good point, we could atleast for the kubeadm cluster deployment as a first step. |
e2e6bf3
to
6a614e7
Compare
/test e2e-kubeadm-ubuntu-jammy |
@vjayaramrh: The specified target(s) for
Use 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. |
allows for installing nonKIND K8S cluster on ubuntu and fedora for e2e test cases
…ocations Co-authored-by: Vishwanath Jayaraman <[email protected]>
Co-authored-by: Daniel Kostecki <[email protected]>
…ephio-project#46) (nephio-project#296) * add support for installing nonKIND cluster via kubeadm allows for installing nonKIND K8S cluster on ubuntu and fedora for e2e test cases * Add support for installing nonKIND cluster via kubeadm, moving file locations Co-authored-by: Vishwanath Jayaraman <[email protected]> * Change yml file suffix in main --------- Co-authored-by: vjayaramrh <[email protected]>
3ea8634
to
76dbd84
Compare
/test e2e-kubeadm-ubuntu-jammy |
/test e2e-kubeadm-fedora-38 |
@vjayaramrh: The following test failed, say
Full PR test history. Your PR dashboard. 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. |
Co-authored-by: Daniel Kostecki <[email protected]>
- name: e2e-kubeadm-ubuntu-jammy | ||
annotations: | ||
labels: | ||
run_if_changed: '^e2e/' |
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.
Should we refine these. I feel it's overkill running all of these jobs every time there is a change made anywhere in the e2e dir
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 am up for any suggestions, (As a side note, this job is optional for PR merge at the moment)
CC: @radoslawc
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.
@efiacor @vjayaramrh that's my feeling as well, this however would require modularising each job as they are now defined in single place. I've created issue for that: nephio-project/sig-release#47
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.
Okay lets merge this PR and take the other issue in another PR.
- name: e2e-kubeadm-fedora-38 | ||
annotations: | ||
labels: | ||
run_if_changed: '^e2e/' |
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.
as above
HOME=${NEPHIO_HOME:-/home/$NEPHIO_USER} | ||
REPO_DIR=${NEPHIO_REPO_DIR:-$HOME/test-infra} | ||
DOCKERHUB_USERNAME=${DOCKERHUB_USERNAME:-""} | ||
DOCKERHUB_TOKEN=${DOCKERHUB_TOKEN:-""} | ||
FAIL_FAST=${FAIL_FAST:-$(get_metadata fail_fast "false")} | ||
# MGMT_CLUSTER_TYPE is intended to be set by prow jobs |
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.
Is this the case? Where is it set?
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 tagged you and added a comment in .prow.yml file where this is set
@@ -75,6 +75,14 @@ fact_caching_connection = /tmp | |||
EOT | |||
|
|||
# Management cluster creation | |||
if [[ ${MGMT_CLUSTER_TYPE:-kind} == "kubeadm" ]]; then |
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.
Silly question but do we get multiple mgmt clusters if this executes?
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 Google GKE or REd Hat decides to add their clusters to CI/CD, then we could get different types. For now it will just be kind and kubeadm.
- "-c" | ||
- | | ||
set -eE; cd "$(git rev-parse --show-toplevel)/e2e/terraform"; trap 'terraform destroy -target module.gcp-ubuntu-jammy -auto-approve' EXIT; | ||
terraform init && timeout 120m terraform apply -target module.gcp-ubuntu-jammy -var="fail_fast=true" -var="mgmt_cluster_type=kubeadm" -auto-approve |
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.
@efiacor FYI The prow job sets the management cluster type here
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: radoslawc 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 |
/lgtm |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR adds prow job support to deploy Nephio management components on a kubeadm cluster. The files to review as part of this PR are
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Please review and merge #296 prior to merging this PR. This PR includes files from the #296 PR
Does this PR introduce a user-facing change?: