Kubernetes Cloud Connector
Deploy the Trusted Signatures container gateway in Kubernetes or Docker for internal HTTP-based PDF sealing with health checks, scaling, and cluster-managed ingress.
- Kubernetes Deployment + Service + Ingress
- Replica-based scaling
- Pod security context
Kubernetes proof
Run the sealing gateway with cluster-managed speed, scale, and control
The documented Kubernetes pattern uses a containerized HTTP gateway, replica-based scaling, and cluster security controls so platform teams can run sealing behind their own ingress, service, and operational policies.
HTTP
speed path
Applications call a simple `/seal` endpoint over internal HTTP without object-store staging or external orchestration layers.
3
replicas in the example
The documented Kubernetes manifest starts with three replicas behind a Service and Ingress for cluster-managed scaling.
Probe
operational readiness
Liveness and readiness checks on `/health` help the cluster route traffic only to healthy pods.
Hardened
security baseline
The example manifest runs as non-root, disables privilege escalation, and uses a read-only root filesystem.
Kubernetes Cloud Connector Docs
Use these guides to deploy and operate the Kubernetes Cloud Connector inside your own cluster or container environment.
Start here
- User guide: run the container locally, deploy the Kubernetes manifest, and call the
/sealAPI.
Operating model
- Deploy the connector as a Docker container or Kubernetes workload in your own environment.
- Expose the HTTP API through a Service and optional Ingress.
- Scale the deployment with replica count and cluster scheduling.
- Send PDF content directly to the container gateway and receive the sealed PDF back in the response.
Need architectural review?
Book a technical walkthrough
For enterprise rollout, we can review trust model, controls, and integration patterns with your team.