Fix emptyDir sizeLimit handling in our CRDs
#12068
Open
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.
Type of change
Description
#12067 describes a pretty nasty bug in our CRDs. The additional volumes in the Pod template use the native Fabric8
EmptyDirVolumeSourceclass in the API model. However, this class relies on the Fabric8Quantityclass and this class has a structure that our CRDs cannot handle. As a result:This PR creates our own model class to replace the Fabric8
EmptyDirVolumeSource. It does not useQuantity(similarly to our storage configuration) and makes sure the CRDs use the correct layout and Strimzi can handle it.However, strictly speaking, this breaks the compatibility of the API. Given that it:
I think it might be ok to do this. But there is some extent of risk worth considering during the review.
This should resolve #12067
Checklist