-
Notifications
You must be signed in to change notification settings - Fork 64
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
Introduce cluster template with Passt binding #213
Conversation
Pull Request Test Coverage Report for Build 3581237415
💛 - Coveralls |
Signed-off-by: Radim Hrazdil <rhrazdil@redhat.com>
Signed-off-by: Radim Hrazdil <rhrazdil@redhat.com>
So the template can be easily chosen by setting an env variable Signed-off-by: Radim Hrazdil <rhrazdil@redhat.com>
Signed-off-by: Radim Hrazdil <rhrazdil@redhat.com>
Because v0.58.0 doesn't contain the fix (kubevirt/kubevirt#8578) for passt as it advertises. Signed-off-by: Radim Hrazdil <rhrazdil@redhat.com>
16279e4
to
648db22
Compare
/ok-to-test |
Signed-off-by: Radim Hrazdil <rhrazdil@redhat.com>
648db22
to
cf2dd64
Compare
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: davidvossel, rhrazdil 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 this PR does / why we need it:
This PR adds template with VMs using Passt binding to pod network.
Passt featureGate is enabled in kubevirtci script and Passt recommended node configuration is performed on cluster-up.
NOTE: There is a commit bumping kubevirt to 0.59.0-alpha, because while kubevirt/kubevirt#8578 is merged in kubevirt release-0.58 branch, the change hasn't made it to v0.58.0 tag.
Lastly, an e2e test is added to exercise cluster creation with Passt binding.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
Release notes: