Upstream Ca File

Sets a trusted CA bundle for all upstream TLS connections via runtime.upstream_ca_file

Category: Setup-dependent integration
Task: Sets a trusted CA bundle for all upstream TLS connections via runtime.upstream_ca_file

Prerequisites: The external service, credentials, or certificates referenced by this configuration.

Run it: Use ghcr.io/praxis-proxy/praxis:0.7.2 and follow the first reverse-proxy tutorial to mount and start the configuration.

This configuration comes from the selected release. The example has not been run here; external services are not bundled.

Download the source file.

# Global Upstream CA File
#
# Sets a trusted CA bundle for all upstream TLS
# connections via `runtime.upstream_ca_file`. Clusters
# with `tls:` enabled will verify the upstream
# certificate against this CA instead of the system
# trust store.
#
# Use per-cluster `tls.ca.ca_path` instead when
# different clusters trust different CAs.
#
# Note: upstream_ca_file replaces the system trust
# store entirely. Create a combined PEM bundle if you
# need both private and public CAs.
#
# The path is validated at startup, so to use this
# feature add the following to this config (adjusting
# the path to your CA bundle):
#
#   runtime:
#     upstream_ca_file: /etc/praxis/tls/ca-bundle.pem
#
#   Client -> HTTP -> Praxis :8080 -> TLS -> Backend :8443
#
listeners:
  - name: default
    address: "127.0.0.1:8080"
    filter_chains:
      - main

filter_chains:
  - name: main
    filters:
      - filter: router
        routes:
          - path_prefix: "/"
            cluster: backend

      - filter: load_balancer
        clusters:
          - name: backend
            tls:
              sni: "api.example.com"
            endpoints:
              - "127.0.0.1:8443"

insecure_options:
  allow_private_endpoints: true # example proxies to local backends