-
Notifications
You must be signed in to change notification settings - Fork 86
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
Data volume source image #751
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
fd1e856
Support worker config volume source image
hebelsan c00c822
Make generate
hebelsan 648306b
Add docu for worker config sourceImage
hebelsan 43cf20d
Make generate
hebelsan 9802b76
Move imageSource to DataVolume config
hebelsan bfc9b2e
Adjust docu
hebelsan 3dccc37
Use slice.ContainsFunc in validation
hebelsan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -155,6 +155,7 @@ The worker configuration contains: | |
|
||
If you attach the disk with `SCRATCH` type, either an `NVMe` interface or a `SCSI` interface must be specified. | ||
It is only meaningful to provide this volume interface if only `SCRATCH` data volumes are used. | ||
|
||
* Volume Encryption config that specifies values for `kmsKeyName` and `kmsKeyServiceAccountName`. | ||
* The `kmsKeyName` is the | ||
key name of the cloud kms disk encryption key and must be specified if CMEK disk encryption is needed. | ||
|
@@ -166,6 +167,12 @@ The worker configuration contains: | |
gcloud projects add-iam-policy-binding projectId --member | ||
serviceAccount:[email protected] --role roles/cloudkms.cryptoKeyEncrypterDecrypter | ||
``` | ||
|
||
* Setting a volume image with `dataVolume.sourceImage`. | ||
However, this parameter should only be used with particular caution. | ||
For example Gardenlinux works with filesystem LABELs only and creating another disk form the very same image causes the LABELs to be duplicated. | ||
See: https://github.com/gardener/gardener-extension-provider-gcp/issues/323 | ||
|
||
* Service Account with their specified scopes, authorized for this worker. | ||
|
||
Service accounts created in advance that generate access tokens that can be accessed through the metadata server and used to authenticate applications on the instance. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -95,6 +95,8 @@ spec: | |
# encryption: # Encryption Details | ||
# kmsKeyName: "projects/projectId/locations/<zoneName>/keyRings/<keyRingName>/cryptoKeys/alpha" | ||
# kmsKeyServiceAccount: "[email protected]" | ||
# dataVolume: # provider specific dataVolume configuration | ||
# sourceImage: "projects/sap-se-gcp-gardenlinux/global/images/..." | ||
# gpu: | ||
# acceleratorType: nvidia-tesla-t4 | ||
# count: 1 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(apologies for delay in reviewing. was on sick leave.)
Just for confirmation: I assume this new validation routine was introduced since we didn't any validation before to enforce this section in the usage document:
"If you attach the disk with SCRATCH type, either an NVMe interface or a SCSI interface must be specified. It is only meaningful to provide this volume interface if only SCRATCH data volumes are used."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previously, the validation for the SCRATCH disk type was present and has now been slightly refined.
A new validation rule requires that the workerConfigDataVolume name must correspond to a dataVolume name.