Conversation
- Add Envoy proxy sidecars to api, front, and agent components for mTLS - Create cert-manager Certificate CRDs for automatic certificate provisioning - Add Envoy ConfigMaps with listener and cluster configurations - Update services to route through Envoy secure ports when enabled - Update ConfigMaps to route traffic through local Envoy egress - Remove director component (deployment, service, configmap, secrets) - Feature is disabled by default (envoy.enabled: false) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add PostgreSQL deployment, service, PVC, and secrets templates - Add global imagePullSecrets with per-component override fallback - Fix OpenShift UID range in values-openshift.yaml - Remove unused envoy resources and simplify envoy config - Add cert-manager issuer for mTLS certificates Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 enables internal TLS encryption (server TLS only, not mTLS) using only namespace-confined resources (no cluster-level controls). It relies on the available of a cert-manager's certificate issuer: ClusterIssuer or Issuer. It issues certificates for each component, loads them into sidecar Envoys and makes the components talk through these sidecars.
This way, the original components are unchanged. What's changed is what endpoints they use to talk to each other. Every single endpoint is now handled by an Envoy sidecar if the internal TLS is enabled.