Skip to content

Support Importing Volume Over HTTP Using Basic Auth #1878

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

Merged

Conversation

moadqassem
Copy link
Member

What this PR does / why we need it:
One way to import a a virtual machine disk, is via an http endpoint that holds a raw image. So far this method didn't support basic auth to interact with the image repo server that holds these raw images. This PR supports sending the basic auth as a header in the CDI DataVolume object by reading the headers either explicitly from the Machine Deployment spec or referring to a secret that contains those headers.

ExtraHeaders field in the MachineDeployment spec is used to read those headers explicitly and send them as part of the importing request.

ExtraHeadersFromSecret is used to read those headers from a secret that is being referenced in the MachineDeployment object.

Which issue(s) this PR fixes:
/kind feature

Fixes #

What type of PR is this?

Special notes for your reviewer:
This PR has been tested manually and it succeeded.
Does this PR introduce a user-facing change? Then add your Release Note here:

Support `ExtraHeaders  in the KubeVirt Provider 

Documentation:

None

@kubermatic-bot kubermatic-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. docs/none Denotes a PR that doesn't need documentation (changes). dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Nov 17, 2024
@moadqassem moadqassem requested a review from yaa110 November 17, 2024 15:47
Copy link
Member

@cnvergence cnvergence left a comment

Choose a reason for hiding this comment

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

/approve
LGTM

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Nov 18, 2024
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: faa2557f26c3f54301c7db799a3ed7242b2989bd

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cnvergence

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 18, 2024
@kubermatic-bot kubermatic-bot merged commit 86c117a into kubermatic:main Nov 18, 2024
12 checks passed
@moadqassem moadqassem deleted the support-kv-dv-https-basic-auth branch November 18, 2024 10:55
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 Denotes that all commits in the pull request have the valid DCO signoff message. docs/none Denotes a PR that doesn't need documentation (changes). kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants