Integrates with
account required
Kubernetes TLS Secrets
Kubernetes TLS Secrets are created or patched with cert and key data, read back, and previous resourceVersion is kept for rollback. Namespaces are discovered.
Verification: test_verified. Connection: unknown. Credentials: none. Live E2E: no.
No disposable Kubernetes cluster kubeconfig is configured.
What sslcertificates.io can do
Kubernetes TLS Secrets are created or patched with cert and key data, read back, and previous resourceVersion is kept for rollback. Namespaces are discovered. Capabilities: discover_namespaces, upsert_secret, read_secret, rollback. Authentication uses kubeconfig.
Required permissions
A ServiceAccount limited to secrets in selected namespaces. The platform never requests cluster-admin.
Setup
Open Dashboard → Integrations → Kubernetes TLS Secrets. Enter the credentials described on this page. Values are encrypted at rest and never shown again. Run Test connection. Discovery runs only after authentication succeeds. Select a discovered resource. Do not paste opaque IDs unless the provider cannot enumerate them. Perform the certificate or notification action, then confirm the external system matches. Disconnect removes stored credentials and owned test resources created by sslcertificates.io.
Known limitations
The connector writes kubernetes.io/tls secrets only. It does not store CA bundles as Opaque secrets unless asked.
Official sources
Fact checked 2026-09-20. https://kubernetes.io/docs/concepts/configuration/secret/#tls-secrets Kubernetes TLS Secrets is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.
Capabilities
Connect
Kubernetes TLS Secrets is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.