[V2] Set default statefulset image based on securityProfile #693
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.
Proposed changes
This update removes the default CRD validation marker from the
workspace.spec.image
field, allowing for dynamic image selection based on the value ofworkspace.spec.securityProfile
. WhensecurityProfile
is set tobaseline
, the image defaults topulumi/pulumi:latest
. IfsecurityProfile
is marked asrestricted
, the system will instead selectpulumi/pulumi:latest-nonroot
. If a user specifies their own image, then that value is used instead. Handling these default settings within the controller is necessary, as CRD validation markers cannot accommodate conditional defaults.Before implementing this feature, additional ginkgo tests were introduced to confirm that the desired behavior is properly achieved.
Related issues (optional)
Closes: #653