Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable cache for all Kubernetes capabilities #430

Open
jvanz opened this issue Feb 2, 2024 · 2 comments
Open

Disable cache for all Kubernetes capabilities #430

jvanz opened this issue Feb 2, 2024 · 2 comments
Labels
kind/enhancement New feature or request

Comments

@jvanz
Copy link
Member

jvanz commented Feb 2, 2024

Is your feature request related to a problem?

We received a request from the community asking for a way to disable the cache for the Kubernetes capabilities. Currently, we allow users to disable cache only for the kubernetes/get_resource capability.

Solution you'd like

I think we can replicate the behavior of the kubernetes/get_resource capability in the other kubernetes capabilities. By adding a flag in the request struct to flag when the cache should be disabled.

Alternatives you've considered

No response

Anything else?

No response

@jvanz jvanz added the kind/enhancement New feature or request label Feb 2, 2024
@jvanz
Copy link
Member Author

jvanz commented Feb 2, 2024

@brunorene is the user which reported that issue on slack. Is my error description correct?

@brunorene
Copy link

Thank you José, yes this ticket describes the issues. This would be just a tactical solution that would provide the means to get the freshest information from the cluster but it needs to be used carefully because it can overload the cluster.

IMO this ticket would be the best approach to solve the issue, but I understand that it is a much more complex feature/change. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

2 participants