Skip to content

Correct the usage of kubevirtci - #122

Merged
kubevirt-bot merged 11 commits into
kubevirt:mainfrom
Barakmor1:updateci
Mar 4, 2025
Merged

Correct the usage of kubevirtci #122
kubevirt-bot merged 11 commits into
kubevirt:mainfrom
Barakmor1:updateci

Conversation

@Barakmor1

@Barakmor1 Barakmor1 commented Feb 27, 2025

Copy link
Copy Markdown
Member

What this PR does / why we need it:
Instead of copying the content from kubevirtci and adding the KubeVirt installation to make cluster-up, include the relevant kubevirtci content in AAQ and make the KubeVirt installation part of the make cluster-up as a seperated process from the imported kubevirtci process.

This PR was inspired by @enp0s3 work in here

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

NONE

@kubevirt-bot kubevirt-bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/XXL labels Feb 27, 2025
@Barakmor1

Copy link
Copy Markdown
Member Author

Update: Had to remove the Target var from the lane yaml definition :

kubevirt/project-infra#3982

/test pull-aaq-functest

@Barakmor1
Barakmor1 force-pushed the updateci branch 7 times, most recently from b065171 to 4ff5f3c Compare February 27, 2025 14:23
@Barakmor1

Copy link
Copy Markdown
Member Author

/retest-required

1 similar comment
@Barakmor1

Copy link
Copy Markdown
Member Author

/retest-required

Signed-off-by: bmordeha <bmordeha@redhat.com>
@Barakmor1
Barakmor1 force-pushed the updateci branch 3 times, most recently from 1b75b66 to c2838c5 Compare March 2, 2025 11:21

@enp0s3 enp0s3 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Barakmor1 Looks great! I've found some micro nits, please see below, other than that LGTM

Comment thread cluster-sync/install.sh Outdated
fi
}


Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: redundant newline

Comment thread hack/sync-kubevirtci.sh Outdated
# Required for kubevirtci_git_hash
source $(dirname "$0")/config.sh

WASP_DIR="$(

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
WASP_DIR="$(
AAQ_DIR="$(

Comment thread hack/sync-kubevirtci.sh Outdated
download_cluster_up=true
function getClusterUpShasum() {
(
cd ${WASP_DIR}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
cd ${WASP_DIR}
cd ${AAQ_DIR}

Signed-off-by: bmordeha <bmordeha@redhat.com>
Signed-off-by: bmordeha <bmordeha@redhat.com>
Signed-off-by: bmordeha <bmordeha@redhat.com>
added scripts in hack directory to comply with kubevirtci
dependencies

Signed-off-by: bmordeha <bmordeha@redhat.com>
kubevirt deployment moved to cluster-up in
a not autogenerated ./hack/cluster-up.sh file.

sync.sh clean.sh install.sh are now working with
kubevirtci.

KUBEVIRT_RELEASE is now defined in config-kubevirtci.sh

fixed default image url for make manifests
its now the internal registry URL of kubevirtci.

Signed-off-by: bmordeha <bmordeha@redhat.com>
Signed-off-by: bmordeha <bmordeha@redhat.com>
Without setting it we violates PodSecurity "restricted:latest"
Includeing the sidecar container for plugable policies in
the function tests

Since k8s > version 1.30

Signed-off-by: bmordeha <bmordeha@redhat.com>
Signed-off-by: bmordeha <bmordeha@redhat.com>
Signed-off-by: bmordeha <bmordeha@redhat.com>
Signed-off-by: bmordeha <bmordeha@redhat.com>

@enp0s3 enp0s3 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
@Barakmor1 Thank you!

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 4, 2025
@Barakmor1

Copy link
Copy Markdown
Member Author

/approve

@kubevirt-bot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Barakmor1

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 4, 2025
@kubevirt-bot
kubevirt-bot merged commit 6fb0c13 into kubevirt:main Mar 4, 2025
@Barakmor1

Copy link
Copy Markdown
Member Author

/cherrypick release-v1.3

@kubevirt-bot

Copy link
Copy Markdown
Contributor

@Barakmor1: new pull request created: #123

Details

In response to this:

/cherrypick release-v1.3

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.

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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/XXL

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants