Search Options

Results per page
Sort
Preferred Languages
Advance

Results 141 - 150 of 436 for secrets (0.06 sec)

  1. helm-releases/minio-3.3.2.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 Dec 28 19:28:13 UTC 2025
    - Last Modified: Sat Dec 11 17:26:01 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  2. helm-releases/minio-3.3.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...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sat Dec 11 17:59:34 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  3. helm-releases/minio-1.0.2.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 Dec 28 19:28:13 UTC 2025
    - Last Modified: Tue Aug 24 18:58:05 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  4. helm-releases/minio-5.3.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 Dec 28 19:28:13 UTC 2025
    - Last Modified: Fri Oct 11 12:21:05 UTC 2024
    - 21.7K bytes
    - Viewed (0)
  5. docs/sts/client-grants.md

    export MINIO_IDENTITY_OPENID_CLIENT_ID="843351d4-1080-11ea-aa20-271ecba3924a"
    minio server /mnt/export
    ```
    
    Testing with an example
    > Obtaining client ID and secrets follow [Keycloak configuring documentation](https://github.com/minio/minio/blob/master/docs/sts/keycloak.md)
    
    ```
    $ go run client-grants.go -cid PoEgXP6uVO45IsENRngDXj5Au5Ya -csec eKsw6z8CtOJVBtrOWvhRWL4TUCga
    
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Tue Aug 12 18:20:36 UTC 2025
    - 7.2K bytes
    - Viewed (0)
  6. helm-releases/minio-3.5.1.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 Dec 28 19:28:13 UTC 2025
    - Last Modified: Fri Feb 04 22:54:20 UTC 2022
    - 15.4K bytes
    - Viewed (0)
  7. helm-releases/minio-3.5.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...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Wed Feb 02 00:16:41 UTC 2022
    - 15.2K bytes
    - Viewed (0)
  8. helm-releases/minio-3.1.7.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 Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Oct 03 22:23:22 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  9. helm-releases/minio-3.3.1.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 Dec 28 19:28:13 UTC 2025
    - Last Modified: Thu Dec 02 20:09:18 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  10. .github/workflows/codeql-analysis.yml

          env:
            # Set the DEVELOCITY_ACCESS_KEY so that a Build Scan is generated
            DEVELOCITY_ACCESS_KEY: ${{ secrets.DEVELOCITY_ACCESS_KEY }}
            # Potential stop-gap solution for ReadTimeout issues with the Gradle Build Cache
            # https://gradle.slack.com/archives/CHDLT99C6/p1636477584059200
            GRADLE_OPTS: -Dhttp.keepAlive=false
    Registered: Wed Dec 31 11:36:14 UTC 2025
    - Last Modified: Thu Dec 11 22:12:03 UTC 2025
    - 4K bytes
    - Viewed (0)
Back to top