Apply our customizations on top of upstream release-2.7 #612
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.
Towards https://github.com/giantswarm/giantswarm/issues/32021
I pushed the latest
upstream/release-2.7
as our fork'srelease-2.7
branch. This PR adds our fork changes on top. Seems that only the S3 Ignition support must be added and everything else is contained in v2.7.x already (judging from the commits in our previous release-2.5 upgrade PR, as also listed incluster-api-provider-aws-app/helm/cluster-api-provider-aws/values.yaml
).(Not tested yet at time of PR creation, but will be soon.)