Skip to content

Conversation

@nunnatsa
Copy link

@nunnatsa nunnatsa commented Jan 8, 2026

Release notes:

Sync upstream 2026-01-08

nunnatsa and others added 30 commits April 23, 2025 09:25
Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
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>
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>
Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
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>
…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>
@nunnatsa
Copy link
Author

nunnatsa commented Jan 8, 2026

/test e2e-hypershift-kubevirt

2 similar comments
@nunnatsa
Copy link
Author

nunnatsa commented Jan 8, 2026

/test e2e-hypershift-kubevirt

@nunnatsa
Copy link
Author

nunnatsa commented Jan 8, 2026

/test e2e-hypershift-kubevirt

@nunnatsa nunnatsa changed the title Sync upstream 2026-01-08 CNV-76225: Sync upstream 2026-01-08 Jan 8, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 8, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 8, 2026

@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.

Details

In response to this:

Release notes:

Sync upstream 2026-01-08

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.

@nunnatsa
Copy link
Author

nunnatsa commented Jan 8, 2026

/test e2e-hypershift-kubevirt

7 similar comments
@nunnatsa
Copy link
Author

nunnatsa commented Jan 8, 2026

/test e2e-hypershift-kubevirt

@nunnatsa
Copy link
Author

nunnatsa commented Jan 8, 2026

/test e2e-hypershift-kubevirt

@nunnatsa
Copy link
Author

nunnatsa commented Jan 8, 2026

/test e2e-hypershift-kubevirt

@nunnatsa
Copy link
Author

nunnatsa commented Jan 8, 2026

/test e2e-hypershift-kubevirt

@nunnatsa
Copy link
Author

nunnatsa commented Jan 8, 2026

/test e2e-hypershift-kubevirt

@nunnatsa
Copy link
Author

nunnatsa commented Jan 8, 2026

/test e2e-hypershift-kubevirt

@nunnatsa
Copy link
Author

nunnatsa commented Jan 8, 2026

/test e2e-hypershift-kubevirt

@nunnatsa
Copy link
Author

nunnatsa commented Jan 9, 2026

/retest

@nunnatsa
Copy link
Author

/test e2e-hypershift-kubevirt

@clebs
Copy link
Member

clebs commented Jan 13, 2026

/retest

Now that image for e2e is fixed: openshift/release#73438

@nunnatsa
Copy link
Author

/retest

5 similar comments
@nunnatsa
Copy link
Author

/retest

@wewang58
Copy link

/retest

@clebs
Copy link
Member

clebs commented Jan 22, 2026

/retest

@clebs
Copy link
Member

clebs commented Jan 22, 2026

/retest

@clebs
Copy link
Member

clebs commented Jan 22, 2026

/retest

@nunnatsa
Copy link
Author

/test pull-ci-openshift-cluster-api-provider-kubevirt-main-e2e-hypershift-kubevirt

@openshift-ci
Copy link

openshift-ci bot commented Jan 23, 2026

@nunnatsa: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test e2e-hypershift-kubevirt
/test images
/test unit-tests

Use /test all to run all jobs.

Details

In response to this:

/test pull-ci-openshift-cluster-api-provider-kubevirt-main-e2e-hypershift-kubevirt

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.

@nunnatsa
Copy link
Author

/test e2e-hypershift-kubevirt

2 similar comments
@qinqon
Copy link

qinqon commented Jan 23, 2026

/test e2e-hypershift-kubevirt

@damdo
Copy link
Member

damdo commented Jan 24, 2026

/test e2e-hypershift-kubevirt

@openshift-ci
Copy link

openshift-ci bot commented Jan 24, 2026

@nunnatsa: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-hypershift-kubevirt cf45e2f link true /test e2e-hypershift-kubevirt

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.