Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[release-v0.26] Windows 11: enable TPM and EFI persistence #641

Closed
wants to merge 3 commits into from
Closed

[release-v0.26] Windows 11: enable TPM and EFI persistence #641

wants to merge 3 commits into from

Conversation

kubevirt-bot
Copy link
Contributor

This is an automated cherry-pick of #611

/assign fossedihelm

Windows 11 now defaults to persistent TPM and EFI. This requires a storage class capable of ReadWriteMany Filesystem

@jean-edouard
Windows 11: enable TPM and EFI persistence
0f4c41a 
The Windows 11 template enables TPM and EFI, since both a required.
However, they were both non-persistent by default, which means bitlocker won't work.
Also, in recent versions of Windows 11, bitlocker requires both TPM and EFI to be persistent.
This enables persistent EFI and TPM, which requires a RWO FS storage class to be present.

Signed-off-by: Jed Lejosne <[email protected]>
@jean-edouard
Windows 2k22: enable TPM and EFI persistence
af3b862 
Signed-off-by: Jed Lejosne <[email protected]>
@jean-edouard
test.sh: add VMPersistentState feature gate
8e61b36 
Signed-off-by: Jed Lejosne <[email protected]>
@kubevirt-bot kubevirt-bot mentioned this pull request Nov 20, 2024
Merged
@kubevirt-bot kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Nov 20, 2024
@ksimon1
Copy link
Member

ksimon1 commented Nov 22, 2024

/retest

1 similar comment
@ksimon1
Copy link
Member

ksimon1 commented Nov 23, 2024

/retest

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Nov 23, 2024

@kubevirt-bot: The following tests 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-gcp-common-templates-windows2016 8e61b36 link true /test e2e-gcp-common-templates-windows2016
ci/prow/e2e-gcp-common-templates-windows2019 8e61b36 link true /test e2e-gcp-common-templates-windows2019
ci/prow/e2e-gcp-common-templates-windows10 8e61b36 link true /test e2e-gcp-common-templates-windows10

Full PR test history. Your PR dashboard.

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.

0xFelix
0xFelix reviewed Nov 25, 2024
View reviewed changes
Copy link
Member

@0xFelix 0xFelix left a comment

Choose a reason for hiding this comment

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

/approve

@kubevirt-bot
Copy link
Contributor Author

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 0xFelix

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 25, 2024
@fossedihelm
Copy link
Contributor

/hold
Investigating on if it is feasible or not since persistent tpm was introduced in release-1.1

@kubevirt-bot kubevirt-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 25, 2024
@fossedihelm
Copy link
Contributor

/hold Investigating on if it is feasible or not since persistent tpm was introduced in release-1.1

/close

@kubevirt-bot
Copy link
Contributor Author

@fossedihelm: Closed this PR.

In response to this:

/hold Investigating on if it is feasible or not since persistent tpm was introduced in release-1.1

/close

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
Reviewers

@0xFelix 0xFelix 0xFelix left review comments

@lyarwood lyarwood Awaiting requested review from lyarwood

Assignees

@fossedihelm fossedihelm

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@kubevirt-bot @ksimon1 @fossedihelm @0xFelix @jean-edouard