You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default image of glvd-postgres sets up tls which increases the complexity of the setup. Considering that we don't want to expose the database, this would only encrypt cluster-internal traffic. I'm not sure if we really need this.
The original design of glvd assume the db is exposed for the ingestion process, but we don't need that. The design is to run the ingestion process inside the cluster so the db does not need to accept any connections from outside the cluster.
The text was updated successfully, but these errors were encountered:
The default image of glvd-postgres sets up tls which increases the complexity of the setup. Considering that we don't want to expose the database, this would only encrypt cluster-internal traffic. I'm not sure if we really need this.
The original design of glvd assume the db is exposed for the ingestion process, but we don't need that. The design is to run the ingestion process inside the cluster so the db does not need to accept any connections from outside the cluster.
The text was updated successfully, but these errors were encountered: