feat: Removed skr permission and cache config for remote kyma & ModuleTemp… #2198
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
kyma-bot
added
cla: yes
medmes
changed the title
10 tasks
medmes
changed the title
lindnerby
requested changes
Jan 23, 2025
kyma-bot
added
size/L
medmes
force-pushed
the
feat/cache_check
branch
from
90ad66f to
bd5efdf
Compare
lindnerby
approved these changes
Jan 23, 2025
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.
Description
After investigation , When using the default client configuration(which is the normal behaviour we use) there's no possibility to verify if the resource is retrieved by infomrer queue. or from a direct API read.
The only way, is to roll out the resources cache configuration and test it by observing metrics on Stage.
Changes proposed in this pull request:
Related issue(s)
#2083