Search Options

Results per page
Sort
Preferred Languages
Advance

Results 131 - 140 of 351 for YAML (0.03 sec)

  1. istioctl/pkg/kubeinject/kubeinject.go

    		Example: `  # Update resources on the fly before applying.
      kubectl apply -f <(istioctl kube-inject -f <resource.yaml>)
    
      # Create a persistent version of the deployment with Istio sidecar injected.
      istioctl kube-inject -f deployment.yaml -o deployment-injected.yaml
    
      # Update an existing deployment.
      kubectl get deployment -o yaml | istioctl kube-inject -f - | kubectl apply -f -
    
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Thu Aug 15 16:31:46 UTC 2024
    - 21K bytes
    - Viewed (0)
  2. helm-releases/minio-3.0.1.tgz

    command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Sep 02 01:47:43 UTC 2021
    - 13.8K bytes
    - Viewed (0)
  3. helm-releases/minio-3.0.2.tgz

    command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Fri Sep 03 08:11:32 UTC 2021
    - 13.8K bytes
    - Viewed (0)
  4. helm-releases/minio-3.1.9.tgz

    command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sun Oct 10 21:28:04 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  5. helm-releases/minio-3.3.0.tgz

    command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Nov 25 17:33:26 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  6. helm-releases/minio-3.4.0.tgz

    command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sun Dec 19 22:32:49 UTC 2021
    - 14.8K bytes
    - Viewed (0)
  7. helm-releases/minio-3.4.1.tgz

    command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Mon Dec 20 21:11:50 UTC 2021
    - 15.2K bytes
    - Viewed (0)
  8. helm/minio/README.md

    ```bash
    helm get values my-release > old_values.yaml
    ```
    
    Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using
    
    ```bash
    helm upgrade -f old_values.yaml my-release minio/minio
    ```
    
    Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy.
    
    ### Configuration
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Wed Jan 24 07:27:57 UTC 2024
    - 10.9K bytes
    - Viewed (0)
  9. istioctl/pkg/admin/istiodconfig.go

    		}
    		return w.Flush()
    	case "json", "yaml":
    		outputBytes, err := json.MarshalIndent(&resultScopeLogLevel, "", "  ")
    		outputBytes = append(outputBytes, []byte("\n")...)
    		if err != nil {
    			return err
    		}
    		if ga.outputFormat == "yaml" {
    			if outputBytes, err = yaml.JSONToYAML(outputBytes); err != nil {
    				return err
    			}
    		}
    		_, err = out.Write(outputBytes)
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Sat Apr 13 05:23:38 UTC 2024
    - 13.5K bytes
    - Viewed (0)
  10. .github/workflows/mint.yml

                 docker-compose -f ${GITHUB_WORKSPACE}/.github/workflows/mint/minio-${mode}.yaml rm || true
              done
    
              docker-compose -f ${GITHUB_WORKSPACE}/.github/workflows/multipart/docker-compose-site1.yaml rm -s -f || true
              docker-compose -f ${GITHUB_WORKSPACE}/.github/workflows/multipart/docker-compose-site2.yaml rm -s -f || true
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Tue Jun 04 15:12:57 UTC 2024
    - 2.9K bytes
    - Viewed (0)
Back to top