feat: Ensure than spec.resources for a pod is supported on the host cluster before syncing it #3440
+149
−0
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 issue type does this pull request address? (keep at least one, remove the others)
/kind enhancement
What does this pull request do? Which issues does it resolve? (use
resolves #<issue_number>if possible)The MR ensure that the
spec.resourcesfor a pod is only synced on the host cluster when supported. It is supported in beta starting version1.34.0resolves #ENG-8682
Please provide a short message that should be published in the vcluster release notes
Fixed an issue where vcluster ...
What else do we need to know?
Note
Adds host-version awareness to pod translation to avoid using unsupported pod-level resources on older clusters.
ServerVersionintranslatorand duringTranslatedropspPod.Spec.Resourceswhen host <v1.34.0util/versionandversion.InfoTestPodResourcesTranslationcovering versions above/below 1.34 and configures fake discovery client in test utilitiesWritten by Cursor Bugbot for commit e2cfecf. This will update automatically on new commits. Configure here.