-
Notifications
You must be signed in to change notification settings - Fork 40
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
add support for installing nonKIND cluster via kubeadm (previously PR #46) #296
Conversation
allows for installing nonKIND K8S cluster on ubuntu and fedora for e2e test cases
/test provision-linter |
This has now been tested on Fedora and the linter errors fixed, I squashed this as best as possible, but feel free to merge it with a squash if it ends up approved to get the log cleaner. |
…ocations Co-authored-by: Vishwanath Jayaraman <vjayaram@redhat.com>
/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 |
/test e2e-free5gc-fedora-34 |
/test e2e-free5gc-fedora-34 |
- name: Hold kubectl | ||
ansible.builtin.dpkg_selections: | ||
name: kubectl | ||
selection: hold |
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.
Updating my comment: My comment is only for workload cluster not for management cluster.
sudo sysctl vm.mmap_rnd_bits=28
, earlier we had to do this for Ubuntu 22 on GCP which has the new 6.5-gcp kernel.
Reason: actions/runner-images#9491 (comment)
So for the OAI packages that we are using in R3 we have to do this, but with the newer OAI images, we don't need any changes.
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.
By the way, the changes that this MR made, I don't think are tested in the CI.
/lgtm |
…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 <vjayaram@redhat.com> * Change yml file suffix in main --------- Co-authored-by: vjayaramrh <vjayaram@redhat.com>
* 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 <vjayaram@redhat.com> * adds prow job to install Nephio components on kubeadm cluster Co-authored-by: Daniel Kostecki <dkosteck@redhat.com> * add support for installing nonKIND cluster via kubeadm (previously PR #46) (#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 <vjayaram@redhat.com> * Change yml file suffix in main --------- Co-authored-by: vjayaramrh <vjayaram@redhat.com> * adds prow job to install nephio components on kubeadm cluster Co-authored-by: Daniel Kostecki <dkosteck@redhat.com> --------- Co-authored-by: Daniel Kostecki <dkosteck@redhat.com> Co-authored-by: Daniel Kostecki <84861140+dkosteck@users.noreply.github.com>
What type of PR is this?
/kind feature
What this PR does / why we need it:
allows for installing nonKIND K8S cluster on ubuntu and fedora for e2e test cases (previously #46)
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
The linked PR authored by @vjayaramrh was automatically closed when the branch was merged/rebased, and does not reflect current files in kubeadm, so it has been linked for historical purposes/to review previous discussions.
Does this PR introduce a user-facing change?: