- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 539 for secret (0.6 sec)
-
internal/kms/secret-key.go
// KMS that uses s as builtin single key as KMS implementation. func ParseSecretKey(s string) (*KMS, error) { v := strings.SplitN(s, ":", 2) if len(v) != 2 { return nil, errors.New("kms: invalid secret key format") } keyID, b64Key := v[0], v[1] key, err := base64.StdEncoding.DecodeString(b64Key) if err != nil { return nil, err } return NewBuiltin(keyID, key) }
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Mon Apr 21 16:23:51 UTC 2025 - 8.4K bytes - Viewed (0) -
internal/kms/secret-key_test.go
Harshavardhana <******@****.***> 1744208919 -0700
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Wed Apr 09 14:28:39 UTC 2025 - 2.9K bytes - Viewed (0) -
docs/tls/kubernetes/README.md
For testing purposes, here is [how to create self-signed certificates](https://github.com/minio/minio/tree/master/docs/tls#3-generate-self-signed-certificates). ## 2. Create Kubernetes secret [Kubernetes secrets](https://kubernetes.io/docs/concepts/configuration/secret) are intended to hold sensitive information.
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 3K bytes - Viewed (0) -
helm-releases/minio-3.6.4.tgz
displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Apr 12 01:30:28 UTC 2022 - 17.9K bytes - Viewed (0) -
helm-releases/minio-4.0.13.tgz
displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Tue Aug 23 18:18:14 UTC 2022 - 19.5K bytes - Viewed (0) -
helm-releases/minio-4.0.5.tgz
displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sat Jul 16 06:42:56 UTC 2022 - 18.3K bytes - Viewed (0) -
helm-releases/minio-4.0.8.tgz
displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Fri Jul 29 23:39:54 UTC 2022 - 18.6K bytes - Viewed (0) -
helm-releases/minio-4.0.12.tgz
displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Aug 14 05:50:43 UTC 2022 - 19.4K bytes - Viewed (0) -
helm-releases/minio-5.0.8.tgz
displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Thu Apr 13 21:49:51 UTC 2023 - 20.3K bytes - Viewed (0) -
helm-releases/minio-5.0.9.tgz
displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Wed May 03 06:23:26 UTC 2023 - 20.2K bytes - Viewed (0)