[MANIFEST] Turning off TLS verification on kubernetes filter #2206
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.
What happens when your PR merges?
The Fluent Bit kubernetes filter will have TLS verification disabled when talking to the kubelet. TLS is still enforced, but we do not verify the certificate... This is to test the TLS verification error we are receiving on fluent bit startup.
What are you changing?
Provide some background on the changes
Re: TLS errors in fluent bit.