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.

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

terraform/vsphere: Inherit firmware settings from the template VM #1445

Merged
merged 1 commit into from
Aug 13, 2021

Conversation

xmudrii
Copy link
Member

@xmudrii xmudrii commented Aug 13, 2021

What this PR does / why we need it:

This PR modifies the Terraform configs for vSphere to inherit the firmware settings from the template VM. By default, BIOS is used as firmware:

firmware - (Optional) The firmware interface to use on the virtual machine. Can be one of bios or EFI. Default: bios.

This can cause a problem if the template was created with EFI. In that case, the created machine would use BIOS and it could be unbootable because the template machine was configured as an EFI machine.

Does this PR introduce a user-facing change?:

Inherit the firmware settings from the template VM in the Terraform configs for vSphere

/assign @kron4eg

Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
@xmudrii xmudrii requested a review from kron4eg August 13, 2021 16:10
@kubermatic-bot kubermatic-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. labels Aug 13, 2021
@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xmudrii

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Aug 13, 2021
@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Aug 13, 2021
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: bd43d071888b5252e2a0609ccfd8f116e08889b9

@kubermatic-bot kubermatic-bot merged commit 8a93303 into master Aug 13, 2021
@kubermatic-bot kubermatic-bot added this to the KubeOne 1.3 milestone Aug 13, 2021
@kubermatic-bot kubermatic-bot deleted the vsphere-firmware branch August 13, 2021 16:19
hwuethrich added a commit to hwuethrich/kubeone that referenced this pull request Aug 26, 2021
* upstream/master:
  Increase the minimum Kubernetes version to v1.19 (kubermatic#1466)
  Automatically deploy CSI plugin and driver for supported providers, and add support for OpenStack Cinder CSI (kubermatic#1465)
  Add support for versioned images (kubermatic#1463)
  Add changelog for v1.3.0-alpha.1 release (kubermatic#1460)
  Use kubeadm/v1beta3 API for Kubernetes 1.22+ clusters (kubermatic#1457)
  Enable PodSecurity admission controller for 1.22 clusters (kubermatic#1456)
  Add Kubernetes 1.22 tests and remove 1.18 tests (kubermatic#1447)
  Extend restart API server script to handle failing crictl logs (kubermatic#1448)
  Remove upx from the kubeone-e2e image (kubermatic#1443)
  terraform/vsphere: Inherit firmware settings from the template VM (kubermatic#1445)
  Update machine-controller to v1.35.1 (kubermatic#1440)
  Redirect push-e2e-image job failures to the appropriate channel (kubermatic#1442)
  Update images (kubermatic#1441)
  Azure CCM (kubermatic#1438)
  Upgrade machine-controller to v1.35.0 (kubermatic#1437)
  Check if unzip is present on the current system. (kubermatic#1435)
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. 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. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants