This repository has been archived by the owner on Jan 19, 2022. It is now read-only.
Add ability to generate ingress resources. #14
Merged
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.
Add the ability to generate ingress resources, either
OneToOne where a k8s ingress resource is created for each
node (1:1), or OneToMany (1:N) where one ingress resource is created
for all quorum nodes deployed in the cluster, and all nodes share a
common host name.
Currently only support one host FQDN per ingress.
Only exposing the geth rpc endpoint.
Not supporting tls at this time, however tls can be added with
self signed certificate (which would requires modification of the
geth client) or using a valid root CA.