Search Options

Results per page
Sort
Preferred Languages
Advance

Results 51 - 60 of 112 for reflow (0.22 sec)

  2. github.com/minio/minio

    helm-releases/minio-4.0.12.tgz 

    "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
    Others
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Sun Aug 14 05:50:43 GMT 2022
    - 19.4K bytes
    - Viewed (0)
  3. github.com/minio/minio

    helm-releases/minio-4.0.7.tgz 

    "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
    Others
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Thu Jul 28 03:54:38 GMT 2022
    - 18.6K bytes
    - Viewed (0)
  4. github.com/minio/minio

    helm-releases/minio-5.0.6.tgz 

    "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
    Others
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Mon Feb 13 06:53:06 GMT 2023
    - 20.3K bytes
    - Viewed (0)
  5. github.com/minio/minio

    helm-releases/minio-5.0.3.tgz 

    "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
    Others
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Mon Dec 19 08:53:02 GMT 2022
    - 20.3K bytes
    - Viewed (0)
  6. github.com/minio/minio

    helm-releases/minio-5.0.9.tgz 

    "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
    Others
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Wed May 03 06:23:26 GMT 2023
    - 20.2K bytes
    - Viewed (0)
  7. github.com/istio/istio

    operator/cmd/mesh/testdata/manifest-generate/data-snapshot.tar.gz 

    adding its own resources # block in the relevant section below and setting the desired resources values. defaultResources: requests: cpu: 10m # memory: 128Mi # limits: # cpu: 100m # memory: 128Mi # Default node tolerations to be applied to all deployments so that all pods can be # scheduled to a particular nodes with matching taints. Each component can overwrite # these default values by adding its tolerations block in the relevant section below # and setting the desired values. # Configure this field...
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Wed Jan 10 05:10:03 GMT 2024
    - 198.1K bytes
    - Viewed (1)
  8. github.com/istio/istio

    manifests/profiles/default.yaml 

        ingressGateways:
    - name: istio-ingressgateway
      enabled: true
    egressGateways:
    - name: istio-egressgateway
      enabled: false

  # Most default values come from the helm chart's values.yaml
  # Below are the things that differ
  values:
    defaultRevision: ""
    global:
      istioNamespace: istio-system
      configValidation: true
    gateways:
      istio-ingressgateway: {}
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Fri Feb 23 00:16:21 GMT 2024
    - 744 bytes
    - Viewed (0)
  9. github.com/tensorflow/tensorflow

    .github/bot_config.yml 

       
   Apparently, your CPU model does not support AVX instruction sets. You can still use TensorFlow with the alternatives given below:
   
      * Try Google Colab to use TensorFlow.
    Others
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Tue Oct 17 11:48:07 GMT 2023
    - 4K bytes
    - Viewed (0)
  10. github.com/istio/istio

    manifests/charts/istiod-remote/values.yaml 

        # Horizontal Pod Autoscaler will be able to function (if set).
    # Each component can overwrite these default values by adding its own resources
    # block in the relevant section below and setting the desired resources values.
    defaultResources:
      requests:
        cpu: 10m
      #   memory: 128Mi
      # limits:
      #   cpu: 100m
      #   memory: 128Mi
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Apr 22 22:00:40 GMT 2024
    - 20.2K bytes
    - Viewed (0)
  11. github.com/minio/minio

    helm-releases/minio-3.0.2.tgz 

    "ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
    Others
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Fri Sep 03 08:11:32 GMT 2021
    - 13.8K bytes
    - Viewed (0)
Back to top