This repository was archived by the owner on Apr 10, 2024. It is now read-only.
Use HTTP/1.1 to perform readiness check#156
Merged
csviri merged 3 commits intojava-operator-sdk:mainjava-operator-sdk/jenvtest:mainfrom Jan 18, 2024
adriansuarez:asuarez/suppress-goaway-erroradriansuarez/jenvtest:asuarez/suppress-goaway-errorCopy head branch name to clipboard
Merged
Use HTTP/1.1 to perform readiness check#156csviri merged 3 commits intojava-operator-sdk:mainjava-operator-sdk/jenvtest:mainfrom adriansuarez:asuarez/suppress-goaway-erroradriansuarez/jenvtest:asuarez/suppress-goaway-errorCopy head branch name to clipboard
csviri merged 3 commits intojava-operator-sdk:mainjava-operator-sdk/jenvtest:mainfrom
adriansuarez:asuarez/suppress-goaway-erroradriansuarez/jenvtest:asuarez/suppress-goaway-errorCopy head branch name to clipboard
Conversation
Contributor
Author
csviri
reviewed
Jan 18, 2024
core/src/main/java/io/javaoperatorsdk/jenvtest/KubeAPIServer.java
Outdated
Show resolved
Hide resolved
csviri
reviewed
Jan 18, 2024
core/src/main/java/io/javaoperatorsdk/jenvtest/process/ProcessReadinessChecker.java
Show resolved
Hide resolved
This change re-enables the readiness check, using HTTP/1.1 instead of HTTP/2 to invoke it. The readiness checks are unauthenticated and are throttled when the feature gate UnauthenticatedHTTP2DOSMitigation is set to true, which is the default starting in Kubernetes 1.29 (see https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates). This was the cause of the "GOAWAY received" errors that have been observed on Kubernetes 1.29. This change also decouples starting of the servers from waiting until they become ready, so that if the readiness check fails due to some error that propagates out of the polling loop (e.g. IOException), the caller is free to catch it and continue waiting.
afd4a55 to
526dffc
Compare
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
This change re-enables the readiness check, using HTTP/1.1 instead of HTTP/2 to invoke it. The readiness checks are unauthenticated and are throttled when the feature gate UnauthenticatedHTTP2DOSMitigation is set to true, which is the default starting in Kubernetes 1.29 (see https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates). This was the cause of the "GOAWAY received" errors that have been observed on Kubernetes 1.29.
This change also decouples starting of the servers from waiting until they become ready, so that if the readiness check fails due to some error that propagates out of the polling loop (e.g. IOException), the caller is free to catch it and continue waiting.