Search Options

Results per page
Sort
Preferred Languages
Advance

Results 71 - 80 of 149 for HAVING (0.1 sec)

  1. helm-releases/minio-3.3.0.tgz

    For more precise policy, set `networkPolicy.allowExternal=true`. This will only allow pods with the generated client label to connect to MinIO. 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 PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-litera...
    Registered: Sun Oct 27 19:28:09 UTC 2024
    - Last Modified: Thu Nov 25 17:33:26 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  2. helm-releases/minio-3.4.0.tgz

    For more precise policy, set `networkPolicy.allowExternal=true`. This will only allow pods with the generated client label to connect to MinIO. 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 PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-litera...
    Registered: Sun Oct 27 19:28:09 UTC 2024
    - Last Modified: Sun Dec 19 22:32:49 UTC 2021
    - 14.8K bytes
    - Viewed (0)
  3. helm-releases/minio-3.4.1.tgz

    For more precise policy, set `networkPolicy.allowExternal=true`. This will only allow pods with the generated client label to connect to MinIO. 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 PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-litera...
    Registered: Sun Oct 27 19:28:09 UTC 2024
    - Last Modified: Mon Dec 20 21:11:50 UTC 2021
    - 15.2K bytes
    - Viewed (0)
  4. docs/en/docs/release-notes.md

    * Allow having empty paths in *path operations* used with `include_router` and a `prefix`.
        * This allows having a router for `/cats` and all its *path operations*, while having one of them for `/cats`.
        * Now it doesn't have to be only `/cats/` (with a trailing slash).
    Registered: Sun Oct 27 07:19:11 UTC 2024
    - Last Modified: Sat Oct 26 16:51:17 UTC 2024
    - 449.4K bytes
    - Viewed (0)
  5. helm-releases/minio-3.6.2.tgz

    9000. For more precise policy, set `networkPolicy.allowExternal=true`. This will only allow pods with the generated client label to connect to MinIO. 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 PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-litera...
    Registered: Sun Oct 27 19:28:09 UTC 2024
    - Last Modified: Thu Mar 17 18:30:55 UTC 2022
    - 17.9K bytes
    - Viewed (0)
  6. src/cmd/asm/internal/asm/parse.go

    		return 0
    	}
    	r, ok := p.registerReference(name)
    	if !ok {
    		return 0
    	}
    	reg := r - p.arch.Register["R0"]
    	if reg < 0 {
    		// Could happen for an architecture having other registers prefixed by R
    		p.errorf("expected g or R0 through R15; found %s", name)
    		return 0
    	}
    	return uint16(reg)
    }
    
    // Note: There are two changes in the expression handling here
    Registered: Tue Oct 29 11:13:09 UTC 2024
    - Last Modified: Wed Sep 04 18:16:59 UTC 2024
    - 36.9K bytes
    - Viewed (0)
  7. helm-releases/minio-4.0.12.tgz

    9000. For more precise policy, set `networkPolicy.allowExternal=true`. This will only allow pods with the generated client label to connect to MinIO. 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 PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-litera...
    Registered: Sun Oct 27 19:28:09 UTC 2024
    - Last Modified: Sun Aug 14 05:50:43 UTC 2022
    - 19.4K bytes
    - Viewed (0)
  8. helm-releases/minio-4.0.13.tgz

    9000. For more precise policy, set `networkPolicy.allowExternal=true`. This will only allow pods with the generated client label to connect to MinIO. 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 PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-litera...
    Registered: Sun Oct 27 19:28:09 UTC 2024
    - Last Modified: Tue Aug 23 18:18:14 UTC 2022
    - 19.5K bytes
    - Viewed (0)
  9. helm-releases/minio-4.0.5.tgz

    9000. For more precise policy, set `networkPolicy.allowExternal=true`. This will only allow pods with the generated client label to connect to MinIO. 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 PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-litera...
    Registered: Sun Oct 27 19:28:09 UTC 2024
    - Last Modified: Sat Jul 16 06:42:56 UTC 2022
    - 18.3K bytes
    - Viewed (0)
  10. helm-releases/minio-4.0.8.tgz

    9000. For more precise policy, set `networkPolicy.allowExternal=true`. This will only allow pods with the generated client label to connect to MinIO. 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 PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-litera...
    Registered: Sun Oct 27 19:28:09 UTC 2024
    - Last Modified: Fri Jul 29 23:39:54 UTC 2022
    - 18.6K bytes
    - Viewed (0)
Back to top