- Sort Score
- Result 10 results
- Languages All
Results 21 - 30 of 76 for Perret (0.25 sec)
-
docs/en/docs/tutorial/extra-models.md
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 7.7K bytes - Viewed (1) -
docs/fr/docs/features.md
* Conçue avec ces standards après une analyse méticuleuse. Plutôt qu'en rajoutant des surcouches après coup. * Cela permet d'utiliser de la **génération automatique de code client** dans beaucoup de langages. ### Documentation automatique
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 11.1K bytes - Viewed (0) -
docs/zh/docs/tutorial/security/oauth2-jwt.md
可以看到如下用户界面: <img src="https://fastapi.tiangolo.com/img/tutorial/security/image07.png"> 用与上一章同样的方式实现应用授权。 使用如下凭证: 用户名: `johndoe` 密码: `secret` !!! check "检查" 注意,代码中没有明文密码**`secret`**,只保存了它的哈希值。 <img src="https://fastapi.tiangolo.com/img/tutorial/security/image08.png"> 调用 `/users/me/` 端点,收到下面的响应: ```JSON { "username": "johndoe",
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Jan 11 21:21:35 GMT 2024 - 9.2K bytes - Viewed (0) -
common-protos/k8s.io/api/extensions/v1beta1/generated.proto
// wildcard host setting for the loadbalancer controller fulfilling this // Ingress, if left unspecified. // +optional repeated string hosts = 1; // SecretName is the name of the secret used to terminate SSL traffic on 443. // Field is left optional to allow SSL routing based on SNI hostname alone. // If the SNI host in a listener conflicts with the "Host" header field used
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 45.6K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.24.md
`Not-ready` state when credentials for vCenter stored in a secret and Zones feature is in use. Zone labels setup moved to KCM component, kubelet skips this step during startup in such case. If credentials stored in cloud-provider config file as plaintext current behaviour does not change and no action required. For proper functioning `kube-system:vsphere-legacy-cloud-provider` should be allowed to update node object if vCenter credentials stored in secret and Zone feature used. ([#101028](https://github....
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Thu Aug 24 00:02:43 GMT 2023 - 473.4K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.25.md
- This release added support for `NodeExpandSecret` for CSI driver client which enables the CSI drivers to make use of this secret while performing node expansion operation based on the user request. Previously there was no secret provided as part of the `nodeexpansion` call, thus CSI drivers did not make use of the same while expanding the volume at the node side. ([#105963](https://github.com/kubernetes/kubernetes/pull/105963),...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Thu Nov 16 11:30:31 GMT 2023 - 419K bytes - Viewed (0) -
helm/minio/README.md
This label will be 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 PersistentVolumeClaim. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ```
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Jan 24 07:27:57 GMT 2024 - 10.9K bytes - Viewed (0) -
Dockerfile.release.old_cpu
ENV MINIO_ACCESS_KEY_FILE=access_key \ MINIO_SECRET_KEY_FILE=secret_key \ MINIO_ROOT_USER_FILE=access_key \ MINIO_ROOT_PASSWORD_FILE=secret_key \ MINIO_KMS_SECRET_KEY_FILE=kms_master_key \ MINIO_UPDATE_MINISIGN_PUBKEY="RWTx5Zr1tiHQLwG9keckT0c45M3AGeHD6IvimQHpyRywVWGbP1aVSGav" \ MINIO_CONFIG_ENV_FILE=config.env \
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Mar 30 09:41:56 GMT 2024 - 2.8K bytes - Viewed (0) -
helm/minio/templates/_helper_create_svcacct.txt
set -e ; # fail if we can't read the keys. ACCESS=$(cat /config/rootUser) ; SECRET=$(cat /config/rootPassword) ; set +e ; # The connections to minio are allowed to fail. echo "Connecting to MinIO server: $SCHEME://$MINIO_ENDPOINT:$MINIO_PORT" ; MC_COMMAND="${MC} alias set myminio $SCHEME://$MINIO_ENDPOINT:$MINIO_PORT $ACCESS $SECRET" ; $MC_COMMAND ; STATUS=$? ; until [ $STATUS = 0 ] do
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Mar 28 23:20:50 GMT 2024 - 3.4K bytes - Viewed (0) -
docs/kms/IAM.md
set the env. variable `MINIO_KMS_SECRET_KEY` and start/restart the MinIO server. For more details about KES and how to set it up refer to our [KMS Guide](https://github.com/minio/minio/blob/master/docs/kms/README.md). Instead of configuring an external KMS you can start with a single key by setting the env. variable `MINIO_KMS_SECRET_KEY`. It expects the following format: ```sh MINIO_KMS_SECRET_KEY=<key-name>:<base64-value> ```
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 5.3K bytes - Viewed (0)