K8s: Enable api-server by default #79942
Merged
Conversation
This file contains 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
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 is this feature?
This enables the k8s api server and access to playlists by default.
Why do we need this feature?
This is the first step towards having more features/resources accessible though the k8s API
Who is this feature for?
Currently developers and @grafana/cloud-app-platform-squad. There are no real external changes, but we do need time with the infrastructure running in the real world to help address any concerns.
This feature has been running cloud since early december, including using
kubernetesPlayliststhat has more consequential changes of routing existing /api/playlists to the k8s flavor: http://localhost:3000/apis/playlist.grafana.app/