fix: nightly watch test for aks disconnects #2847
Draft
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
We are getting some suspicious error codes in AKS. This does seem somewhat specific to AKS at the moment but we are going to replicate the timeout/keepAlive options from
@kubernetes/client-nodeto see if this makes a difference. This is only going to be a nightly for now because we are experiencing other 429 issues from the kube-apiserver in other Kubernetes flavors that is likely tied to the lists, this PR will likely increase those errors as it will connect and disconnect more often. We have a solution for the lists by tweaking watch config so this is really just a test for now.Docs
Related Issue
Relates to defenseunicorns/kubernetes-fluent-client#971
Type of change
Checklist before merging