This topic tells you how to enable TLS Ingress to a Space on Tanzu Platform for Kubernetes.
Tanzu Application Engine enables platform teams to ensure that all Ingress traffic to a Space is TLS-encrypted by using a third-party certificate authority (CA) or a self-signed certificate. You can use Vault to provide and integrate third-party CAs.
The Gateway API is a prerequisite for configuring TLS communications in a Space. To install the Gateway API:
The certificate manager is a prerequisite for configuring TLS communications in a Space. To install the certificate manager:
Ensure that the packages that provide networking Capabilities are configured with the necessary CA information.
NoteIf you use multiple cluster groups, either enable Vault for all of them or enable Vault for none of them. Do not enable Vault for only one group or only some groups.
To configure the prerequisites for Ingress to use TLS encryption:
Enter Vault endpoint details by pasting the following YAML snippet into the text field:
clusterIngressCa:
vault:
path: <ingress-policy>/sign/<ingress-role>
server: <vault_url>
caBundle: <server_ca_bundle>
auth:
token: <base64_api_token>
The flags in this snippet are described in the following table:
Flag | Description |
---|---|
path |
This is the signing endpoint path for the Vault server, and is created by Vault’s ingress-role role. |
server |
This is the URL where the Vault server is hosted. For example, https://vault.example.com:8200 . |
caBundle |
This is only required if using HTTPS to access the Vault server, and it must be a base64-encoded CA bundle. |
token |
This is a base64-encoded API access token for accessing the Vault server. |
Click Install Package.
Update the networking Profile that you created when setting up the infrastructure to create an application environment or create a new Profile with this configuration.