-
Notifications
You must be signed in to change notification settings - Fork 7
CNV-76225: Sync upstream 2026-01-08 #338
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
Update slack channel link
The current capk version used by install-capk lacks of the field virtualMachineBootstrapCheck and the installation will fail. Update to the latest version. Signed-off-by: Alice Frosi <afrosi@redhat.com>
Bump version of capk in kubevirtci
This is a manual cherry pick of sharath-srikanth-chellappa PR 330 Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
…-1.11.1 Bump cluster-api to v1.11.1 and support v1beta2 api
Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
Also, set KUBEVIRT_FLANNEL=true Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
Bump all dependencies
Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
e2e: bump boot image to v1.34.1
This will allow compiling in systems with older build images. Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
set go version to lower be generic v1.24, instead of specific v1.24.7
Add new flags to the manager in order to configure: - QPS related fields for the client - leader election leaderDuration, renewDeadline and retryPeriod
Add flags for qps and leaderElection
The current ci code downloads the latest version oc clusterctl. The current capk version does not supported by the latest version of capi. Also, the clusterctl installs the latest cluster-api, bootstrap and control-plane. This PR sets the clusterctl version to 1.11.4, and use the kubectl flags to set the versions of the cluster-api, bootstrap and control-plane to version 1.11.4, in order to fix this issue. Signed-off-by: Nahshon Unna Tsameret <nahsh.ut@gmail.com>
Signed-off-by: Nahshon Unna Tsameret <nahsh.ut@gmail.com>
Signed-off-by: Nahshon Unna Tsameret <nahsh.ut@gmail.com>
Signed-off-by: Nahshon Unna Tsameret <nahsh.ut@gmail.com>
make docker-push requires admin permission to write to the /etc/containers/registries.conf file. Also, it adds new line each time we run the test, where the registry is temporary, within the kubevirtci cluster. This commit uses the --tls-verify flag for the docker push command, instead of this setting. Signed-off-by: Nahshon Unna Tsameret <nahsh.ut@gmail.com>
Fix the ci failures
…or-flags fix: initialize flags required for CAPI operator v0.24.0
Signed-off-by: Nahshon Unna Tsameret <nahsh.ut@gmail.com>
Signed-off-by: Nahshon Unna Tsameret <nahsh.ut@gmail.com>
Signed-off-by: Nahshon Unna Tsameret <nahsh.ut@gmail.com>
After movig to use CAPI v1beta2, capk can't run in systems where old CAPI is installed. This commit adds support in v1beta1 CAPI resources, by first convertiong them to v1beta2. The controller will only watch the capi API version that is installed in the cluster, because trying to watch unknow resources, craches the pod. Signed-off-by: Nahshon Unna Tsameret <nahsh.ut@gmail.com>
Signed-off-by: Nahshon Unna Tsameret <nahsh.ut@gmail.com>
|
/test e2e-hypershift-kubevirt |
2 similar comments
|
/test e2e-hypershift-kubevirt |
|
/test e2e-hypershift-kubevirt |
|
@nunnatsa: This pull request references CNV-76225 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/test e2e-hypershift-kubevirt |
7 similar comments
|
/test e2e-hypershift-kubevirt |
|
/test e2e-hypershift-kubevirt |
|
/test e2e-hypershift-kubevirt |
|
/test e2e-hypershift-kubevirt |
|
/test e2e-hypershift-kubevirt |
|
/test e2e-hypershift-kubevirt |
|
/test e2e-hypershift-kubevirt |
|
/retest |
|
/test e2e-hypershift-kubevirt |
|
/retest Now that image for e2e is fixed: openshift/release#73438 |
|
/retest |
5 similar comments
|
/retest |
|
/retest |
|
/retest |
|
/retest |
|
/retest |
|
/test pull-ci-openshift-cluster-api-provider-kubevirt-main-e2e-hypershift-kubevirt |
|
@nunnatsa: The specified target(s) for Use DetailsIn 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-sigs/prow repository. |
|
/test e2e-hypershift-kubevirt |
2 similar comments
|
/test e2e-hypershift-kubevirt |
|
/test e2e-hypershift-kubevirt |
|
@nunnatsa: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
Release notes: