Add Gzip Compression Option for User Data #649
Draft
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.
What this PR does / why we need it:
This PR introduces a new boolean field,
gzipUserData
, in theRKE2ConfigSpec
, allowing users to enable gzip compression for cloud-init user data in the RKE2 bootstrap process. This change is based on this commit, where gzip compression was controlled via a custom annotation. The difference is, this solution utilizes a simpler approach based on new boolean field.The new
gzipUserData
field allows users to enable gzip compression for user data optionally. Few things to highlight:gzipUserData
boolean field in theRKE2ConfigSpec
.gzipUserData
is set tofalse
, ensuring existing configurations are not affected unless explicitly enabled by the user.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #639
Special notes for your reviewer:
Checklist: