K8sSecret
K8sSecret creates a Kubernetes Secret in the target cluster. Unlike the Kyku Secret resource (which manages cloud provider secrets), K8sSecret maps directly to a native v1.Secret inside the cluster.
Secrets can be populated inline or sourced from an Kyku Secret resource via secretRef.
Config
Section titled “Config”| Property | Type | Required | Description |
|---|---|---|---|
cluster |
KubernetesCluster | string |
✅ | Target cluster |
namespace |
K8sNamespace | string |
❌ | Namespace to create the Secret in |
dependsOn |
string[] |
❌ | Explicit dependency ordering |
data |
Record<string, string> |
❌ | Pre-encoded secret data (base64) |
stringData |
Record<string, string> |
❌ | Plain-text secret data (encoded by Kyku) |
secretType |
string |
❌ | Kubernetes secret type (Opaque, kubernetes.io/dockerconfigjson, etc.) |
secretRef |
Secret |
❌ | Reference to an Kyku Secret resource to populate from |
Example
Section titled “Example”// Inline secret dataconst dbCreds = new K8sSecret({ name: 'db-credentials', cluster: myCluster, namespace: myNamespace, stringData: { username: 'admin', password: 's3cret!', }, secretType: 'Opaque',})
// Sourced from Kyku Secret resourceconst tlsSecret = new K8sSecret({ name: 'tls-certs', cluster: myCluster, secretRef: myKykuSecret, secretType: 'kubernetes.io/tls',})Provider support
Section titled “Provider support”| Provider | Supported |
|---|---|
| Kubernetes | ✅ |
| Hetzner | ❌ |
| DigitalOcean | ❌ |
| AWS | ❌ |
| GCP | ❌ |