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

fix: custom kubeconfigs #1304

Merged
merged 1 commit into from
Jan 10, 2025
Merged

fix: custom kubeconfigs #1304

merged 1 commit into from
Jan 10, 2025

Conversation

adityathebe
Copy link
Member

@adityathebe adityathebe commented Jan 9, 2025

resolves: #1302

The resource watcher & the consumer are already provided with a context that has the
custom kubeconfig set. 
Thus, attempting to fetch the kubeconfig once again within them would result in a secret not found error.

Interestingly, this went unnoticed for the first 5 minutes because the secret would get cached in 
duty's GetSecretFromCache.

@adityathebe adityathebe force-pushed the fix/custom-kube-config-in-scrapers branch from 2625756 to eba85ba Compare January 9, 2025 16:46
@adityathebe adityathebe force-pushed the fix/custom-kube-config-in-scrapers branch from eba85ba to 9aec234 Compare January 9, 2025 16:48
@adityathebe adityathebe requested a review from moshloop January 9, 2025 16:57
@moshloop moshloop merged commit d688572 into main Jan 10, 2025
10 checks passed
@moshloop moshloop deleted the fix/custom-kube-config-in-scrapers branch January 10, 2025 06:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ConsumeKubernetesWatch - failed to apply custom kubeconfig: could not find secret
2 participants