This repository has been archived by the owner on Jan 19, 2022. It is now read-only.
Make geth ws ingress optional. #35
Merged
Conversation
This file contains 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
Websock ingress are not fully supported out of the box by various K8s
services, and users may not want to add ws geth ingresses. When enabling
K8s ingresses do not geth ws by default, but allow ws be enabled in the
config.
service:
Ingress:
ws: true
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Websock ingress are not fully supported out of the box by various K8s services, and users may not want to add ws geth ingresses. When enabling K8s ingresses do not geth ws by default, but allow ws be enabled in the config.
service:
Ingress:
ws: true