[v13] Fixes cache init problem with missing kube_service#25006
Merged
tigrato merged 2 commits intobranch/v13from Apr 24, 2023
Merged
[v13] Fixes cache init problem with missing kube_service#25006tigrato merged 2 commits intobranch/v13from
kube_service#25006tigrato merged 2 commits intobranch/v13from
Conversation
This PR fixes a cache init problem when Teleport 12 Kube/Proxy clients connect to a Teleport 13 cluster and expect to watch the unsupported `kube_service` object. It allows the operation but ignores the resources being watched.
tigrato
force-pushed
the
tigrato/fix-cache-init-kube-service
branch
from
e28719b to
57f519c
Compare
tigrato
changed the title
kube_servicekube_service
espadolini
approved these changes
Apr 24, 2023
r0mant
approved these changes
Apr 24, 2023
Closed
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
3 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 PR fixes a cache init problem when Teleport 12 Kube/Proxy clients connect to a Teleport 13 cluster and expect to watch the unsupported
kube_serviceobject.It allows the operation but ignores the resources being watched.