feat: Split State server with Webhook #11
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.
In some deployment models, we might need to deploy the webhook in the host network. E.g. EKS with tunneling networking where the Control Plane cannot communicate with pods through the pod network.
To facilitate this behavior we'd want to deploy only the webhook in the host network and keep the state grpc server running on the Pod network.
This changeset aims to separate those two components into two different deployables, the state and webhook deployments.
We're changing the chart to accomodate these changes.