- Sort Score
- Result 10 results
- Languages All
Results 41 - 50 of 470 for Decref (0.12 sec)
-
helm-releases/minio-3.1.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...
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Thu Oct 07 05:03:47 UTC 2021 - 14.6K bytes - Viewed (0) -
security/pkg/nodeagent/sds/sdsservice.go
} func (s *sdsservice) Close() { close(s.stop) } // toEnvoySecret converts a security.SecretItem to an Envoy tls.Secret func toEnvoySecret(s *security.SecretItem, caRootPath string, pkpConf *mesh.PrivateKeyProvider) *tls.Secret { secret := &tls.Secret{ Name: s.ResourceName, } var cfg security.SdsCertificateConfig ok := false if s.ResourceName == security.FileRootSystemCACert {
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Sat May 25 00:20:04 UTC 2024 - 10.9K bytes - Viewed (0) -
pkg/serviceaccount/claims_test.go
}, { name: "different uid secret", getter: fakeGetter{serviceAccount, secret, nil, nil}, private: &privateClaims{Kubernetes: kubernetes{Svcacct: ref{Name: "saname", UID: "sauid"}, Secret: &ref{Name: "secretname", UID: "secretuidold"}, Namespace: "ns"}}, expectErr: "secret UID (secretuid) does not match service account secret ref claim (secretuidold)", }, {
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Wed Apr 24 18:25:29 UTC 2024 - 17.9K bytes - Viewed (0) -
pkg/volume/projected/projected_test.go
caseMappingMode := int32(0400) cases := []struct { name string mappings []v1.KeyToPath secret *v1.Secret mode int32 optional bool payload map[string]util.FileProjection success bool }{ { name: "no overrides", secret: &v1.Secret{ Data: map[string][]byte{ "foo": []byte("foo"), "bar": []byte("bar"), }, }, mode: 0644,
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Fri Nov 03 18:40:48 UTC 2023 - 40.5K bytes - Viewed (0) -
helm-releases/minio-3.6.0.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 Jun 16 00:44:34 UTC 2024 - Last Modified: Sun Mar 13 22:44:21 UTC 2022 - 17.9K bytes - Viewed (0) -
helm-releases/minio-3.5.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 Jun 16 00:44:34 UTC 2024 - Last Modified: Thu Mar 03 23:29:03 UTC 2022 - 17.7K bytes - Viewed (0) -
helm-releases/minio-3.6.3.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 Jun 16 00:44:34 UTC 2024 - Last Modified: Thu Mar 24 04:07:15 UTC 2022 - 17.9K bytes - Viewed (0) -
helm-releases/minio-3.5.6.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 Jun 16 00:44:34 UTC 2024 - Last Modified: Sat Feb 19 20:34:14 UTC 2022 - 17.6K bytes - Viewed (0) -
internal/auth/credentials.go
// There is no max length enforcement for access keys accessKeyMaxLen = 20 // Minimum length for MinIO secret key for both server secretKeyMinLen = 8 // Maximum secret key length for MinIO, this // is used when autogenerating new credentials. // There is no max length enforcement for secret keys secretKeyMaxLen = 40 // Alpha numeric table used for generating access keys.
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Tue May 28 17:14:16 UTC 2024 - 12K bytes - Viewed (0) -
pkg/kube/multicluster/secretcontroller.go
log.Infof("processing secret event for secret %s", key) scrt := c.secrets.Get(key.Name, key.Namespace) if scrt != nil { log.Debugf("secret %s exists in informer cache, processing it", key) if err := c.addSecret(key, scrt); err != nil { return fmt.Errorf("error adding secret %s: %v", key, err) } } else { log.Debugf("secret %s does not exist in informer cache, deleting it", key)
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Wed Mar 06 02:13:10 UTC 2024 - 12.7K bytes - Viewed (0)