Skip to content

Add the environment variables for the remaining config keys - #47

Merged
satishweb merged 2 commits into
masterfrom
feature/config-key-env-vars
Oct 21, 2026
Merged

satishweb merged 2 commits into
masterfrom
feature/config-key-env-vars

Conversation

@satishweb

Copy link
Copy Markdown
Owner

The upstream server supports more configuration keys than the ones that were exposed. These were missing:

local_addr
cert
key
tls_client_auth
tls_client_auth_ca

They are exposed now as DOH_SERVER_LOCAL_ADDR, DOH_SERVER_CERT, DOH_SERVER_KEY, DOH_SERVER_TLS_CLIENT_AUTH and DOH_SERVER_TLS_CLIENT_AUTH_CA.

  • The certificate and the key have to be set together, the container refuses to start when only one of them is given.
  • The client authentication needs the certificate authority as well.
  • The health check switches to https when the server runs with TLS, it reads that from the configuration file that is in use.
  • The helm chart got the new variables and a scheme for the probes, the probes are plain http and would fail against a server that runs with TLS.
  • The readme documents the variables and the TLS setup.

The test suite starts a container with a certificate and a key and asserts that it serves https and that the health check passes with it.

Fixes #27

The upstream server supports more configuration keys than the ones that
were exposed. These were missing:

    local_addr
    cert
    key
    tls_client_auth
    tls_client_auth_ca

They are exposed now as DOH_SERVER_LOCAL_ADDR, DOH_SERVER_CERT,
DOH_SERVER_KEY, DOH_SERVER_TLS_CLIENT_AUTH and
DOH_SERVER_TLS_CLIENT_AUTH_CA.

The certificate and the key have to be set together, the container refuses
to start when only one of them is given. The client authentication needs
the certificate authority as well.

The health check switches to https when the server runs with TLS, it reads
that from the configuration file that is in use.

The helm chart got the new variables and a scheme for the probes, the
probes are plain http and would fail against a server that runs with TLS.

The test suite starts a container with a certificate and a key and asserts
that it serves https and that the health check passes with it.

Fixes #27
The server runs as the unprivileged user of the container, so the
certificate and the key have to be readable for it. The test suite now
sets the mode of the files it creates accordingly and the readme documents
the requirement.
@satishweb
satishweb merged commit cb1ddb0 into master Oct 21, 2026
4 checks passed
@satishweb
satishweb deleted the feature/config-key-env-vars branch October 21, 2026 04:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add new env variables for new doh config keys

1 participant