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

Allow specifying full image reference for GCP #1520

Merged
merged 1 commit into from
Jan 3, 2023

Conversation

xmudrii
Copy link
Member

@xmudrii xmudrii commented Dec 27, 2022

What this PR does / why we need it:

We have an issue when creating ARM64-based instances on GCP:

An error of type = InvalidConfiguration, with message = Failed to insert instance: googleapi: Error 400: Invalid resource usage: 'Requested boot disk architecture (X86_64) is not compatible with machine type architecture (ARM64).'., invalidResourceUsage occurred 

It appears that the image we use is only compatible with AMD64-based instances. We would have to use another image with ARM64-based instances, which appears to be projects/ubuntu-os-cloud/global/images/family/ubuntu-2204-lts-arm64.

We could do that by using the custom image option, but the current implementation assumes that the custom image is in the user's project. That's not the case because this image is in the global ubuntu-os-cloud project.

This PR ensures that we can specify custom images in other projects while making sure we don't break backwards compatibility.

What type of PR is this?
/kind feature

Does this PR introduce a user-facing change? Then add your Release Note here:

Allow specifying full image reference (`project/`) for GCP

Documentation:

NONE

Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
@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/osm Denotes a PR or issue as being assigned to SIG OSM. labels Dec 27, 2022
@xmudrii xmudrii requested a review from kron4eg December 27, 2022 11:02
@kubermatic-bot kubermatic-bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Dec 27, 2022
@kron4eg
Copy link
Member

kron4eg commented Dec 27, 2022

/approve
/lgtm

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Dec 27, 2022
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: d66c23800078247c378c768e3111a1d56fa8c85c

Copy link
Member

@ahmedwaleedmalik ahmedwaleedmalik left a comment

Choose a reason for hiding this comment

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

/approve

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahmedwaleedmalik, kron4eg, 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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 3, 2023
@kubermatic-bot kubermatic-bot merged commit 0eaa757 into kubermatic:main Jan 3, 2023
@xmudrii xmudrii deleted the gcp-full-image-ref branch January 3, 2023 12:53
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/osm Denotes a PR or issue as being assigned to SIG OSM. 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.

None yet

4 participants