summaryrefslogtreecommitdiff
path: root/pkg/k8s.io/api
diff options
context:
space:
mode:
authorcdoern <cdoern@redhat.com>2022-06-07 16:37:59 -0400
committerCharlie Doern <cdoern@redhat.com>2022-07-20 12:55:33 -0400
commit438fef1caa26a1f09cd7be341e854d4bd5726c2b (patch)
treee449aceae653fcce93fe38aa38a60d08a95bda1e /pkg/k8s.io/api
parent8c9eff5b12eebe318be1f905562be6a236285caa (diff)
downloadpodman-438fef1caa26a1f09cd7be341e854d4bd5726c2b.tar.gz
podman-438fef1caa26a1f09cd7be341e854d4bd5726c2b.tar.bz2
podman-438fef1caa26a1f09cd7be341e854d4bd5726c2b.zip
kube secret handling for podman play kube
add support for both creating a secret using yaml and mounting a secret as a volume given a yaml file. Kubernetes secrets have a different structure than podman and therefore have to be handeled differently. In this PR, I have introduced the basic usecases of kube secrets with more implementations like env secrets to come! resolves #12396 Signed-off-by: Charlie Doern <cdoern@redhat.com>
Diffstat (limited to 'pkg/k8s.io/api')
-rw-r--r--pkg/k8s.io/api/core/v1/types.go1
1 files changed, 1 insertions, 0 deletions
diff --git a/pkg/k8s.io/api/core/v1/types.go b/pkg/k8s.io/api/core/v1/types.go
index 48f353cc6..39a675dae 100644
--- a/pkg/k8s.io/api/core/v1/types.go
+++ b/pkg/k8s.io/api/core/v1/types.go
@@ -56,6 +56,7 @@ type VolumeSource struct {
// ConfigMap represents a configMap that should populate this volume
// +optional
ConfigMap *ConfigMapVolumeSource `json:"configMap,omitempty"`
+ Secret *SecretVolumeSource
}
// PersistentVolumeClaimVolumeSource references the user's PVC in the same namespace.