A data plane certificate is the wildcard TLS certificate your own data plane presents to everyone who connects to its engines, MCP endpoint, data apps and app registry. You choose one of three ways to get it when you install the plane, so you never have to give the plane write access to a DNS zone you do not want it to touch.

Which names does the certificate cover?

Every address on a plane is one label under a fixed name on the plane’s own domain, so one wildcard per kind of address covers the plane for its whole life. Creating a tenant, an engine or an app never adds a name. A wildcard covers exactly one label, so *.engine.plane1.example.com covers abc.engine.plane1.example.com and nothing deeper.

Choose a mode

A certificate mode is the setting frontDoorTls.mode in your plane’s install values. It decides who issues the certificate and who renews it. Pick existingSecret if your security team issues certificates centrally, and delegatedZone if you want automatic renewal without opening your main DNS zone.

Supply your own certificate

1

Choose the mode and name the Secret

In your install values, set frontDoorTls.mode: existingSecret and secrets.trinoproxyTls.existingSecret: dippr-wildcard. The Secret does not have to exist yet.
2

Find the names it must cover

Render those install values with helm template and read the altimate.ai/front-door-tls-names annotation. It lists every name for the features you turned on, separated by commas. Turning a feature on later adds a name: reissue the certificate to cover it and replace the Secret’s contents, or that feature’s host fails TLS. Nothing checks the Secret against this list for you.
3

Create the Secret

In the plane’s namespace, before you install: kubectl -n <namespace> create secret tls dippr-wildcard --cert=fullchain.pem --key=privkey.pem. The certificate file holds your certificate first, then any intermediates.
4

Install

Install or upgrade the plane with the same values.
Renewing. Replace the Secret’s contents before the certificate expires. The plane picks up the new certificate within about two minutes, with no restart. Its log records the expiry date each time it loads a certificate, and warns once a day from 21 days before expiry. A certificate from a private CA. Every client that connects to the plane must trust your CA: your users’ browsers and AI clients, dip, and pipeline runs. So must the plane’s worker, which crawls each engine for metadata search through its public host. Put the CA bundle in a ConfigMap in the plane’s namespace and name it in the plane’s values:
The worker trusts your CA in addition to the public roots. If the ConfigMap does not exist, the worker does not start.

Delegate a sub-zone

You keep your main zone, such as example.com, closed. You create a sub-zone such as dippr.example.com in Google Cloud DNS, Amazon Route 53 or Azure DNS, add an NS record for it in your main zone, and give cert-manager permission to change records in that sub-zone only. The plane’s domain must be the sub-zone or a name under it, such as plane1.dippr.example.com.
1

Create and delegate the sub-zone

Create the zone, copy its name servers, and add them in your main zone as an NS record named dippr. Check it with dig +short NS dippr.example.com.
2

Grant cert-manager the sub-zone

Through workload identity: roles/dns.admin in the sub-zone’s own project on Google Cloud, record changes on that hosted zone only on AWS, or DNS Zone Contributor on that zone on Azure.
3

Create an issuer

An ACME issuer (Let’s Encrypt, for example) with a DNS-01 solver for dippr.example.com.
4

Point the plane at it

Set frontDoorTls.mode: delegatedZone, frontDoorTls.delegatedZone: dippr.example.com and certManager.issuerRef.name to your issuer, then install or upgrade.
The commands for each cloud and a complete issuer example are in the deployment guide that ships with the chart, under “Front-door certificate”.

What happens if a setting is wrong?

The install stops before anything starts, with a message naming the value to fix: