feat(operator/client): Support feature gate retrieval#1207
Merged
Conversation
Techassi
moved this from Development: In Review
to Development: Done
in Stackable Engineering
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This came up in our last versions meeting. We liked the idea of being able to check which features are enabled and on which Kubernetes version the operator is running to be able to potentially use newer Kubernetes features if available.
This PR adds associated functions to the
Clientto retrieve (enabled/disabled/all) feature gates via the/metricsendpoint of the Kubernetes apiserver. Each feature gate needs to be parsed from a line-based metric into a Rust struct. Parsing is achieved with the help ofwinnow(new dependency).