Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 8 of 8 for Chan (0.13 sec)

  1. manifests/charts/istiod-remote/templates/configmap.yaml

          {{- end }}
    {{- end }}
    
    {{/* We take the mesh config above, defined with individual values.yaml, and merge with .Values.meshConfig */}}
    {{/* The intent here is that meshConfig.foo becomes the API, rather than re-inventing the API in values.yaml */}}
    {{- $originalMesh := include "mesh" . | fromYaml }}
    {{- $mesh := mergeOverwrite $originalMesh .Values.meshConfig }}
    
    {{- if .Values.pilot.configMap }}
    apiVersion: v1
    kind: ConfigMap
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Thu Apr 18 18:16:49 GMT 2024
    - 4.9K bytes
    - Viewed (0)
  2. operator/cmd/mesh/testdata/manifest-generate/data-snapshot.tar.gz

    resources we configure have 1000s of fields; given enough users and bespoke use cases, eventually someone will want to customize every one of those fields. If all fields are exposed in `values.yaml`, we end up with an massive API that is also likely worse than just using the Kubernetes API directly. To avoid this, the project attempts to minimize additions to the `values.yaml` API where possible. If the change is a dynamic runtime configuration, it probably belongs in the [MeshConfig API](https://github...
    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)
  3. manifests/charts/istio-control/istio-discovery/templates/configmap.yaml

          {{- end }}
    {{- end }}
    
    {{/* We take the mesh config above, defined with individual values.yaml, and merge with .Values.meshConfig */}}
    {{/* The intent here is that meshConfig.foo becomes the API, rather than re-inventing the API in values.yaml */}}
    {{- $originalMesh := include "mesh" . | fromYaml }}
    {{- $mesh := mergeOverwrite $originalMesh .Values.meshConfig }}
    
    {{- if .Values.pilot.configMap }}
    apiVersion: v1
    kind: ConfigMap
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Thu Apr 18 18:16:49 GMT 2024
    - 4.9K bytes
    - Viewed (0)
  4. manifests/charts/istio-control/istio-discovery/values.yaml

          # Controls whether or not the untaint controller is active
          enabled: false
          # What namespace the untaint controller should watch for istio-cni pods. This is only required when istio-cni is running in a different namespace than istiod
          namespace: ""
    
        affinity: {}
    
        tolerations: []
    
        cpu:
          targetAverageUtilization: 80
        memory: {}
          # targetAverageUtilization: 80
    
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Apr 22 22:00:40 GMT 2024
    - 20.3K bytes
    - Viewed (0)
  5. manifests/charts/istiod-remote/values.yaml

          # Controls whether or not the untaint controller is active
          enabled: false
          # What namespace the untaint controller should watch for istio-cni pods. This is only required when istio-cni is running in a different namespace than istiod
          namespace: ""
        affinity: {}
        tolerations: []
        cpu:
          targetAverageUtilization: 80
        memory: {}
        # targetAverageUtilization: 80
    
    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)
  6. manifests/charts/istio-cni/templates/clusterrole.yaml

    {{- else if .Values.cni.repair.deletePods }}
      - apiGroups: [""]
        resources: ["pods"]
        verbs: ["delete"]
    {{- else if .Values.cni.repair.labelPods }}
      - apiGroups: [""]
        {{- /* pods/status is less privileged than the full pod, and either can label. So use the lower pods/status */}}
        resources: ["pods/status"]
        verbs: ["patch", "update"]
    {{- end }}
    {{- end }}
    ---
    {{- if .Values.cni.ambient.enabled }}
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Sat May 04 01:55:56 GMT 2024
    - 2.2K bytes
    - Viewed (0)
  7. manifests/charts/gateways/istio-egress/values.yaml

          tolerations: []
    
          # Specify the pod anti-affinity that allows you to constrain which nodes
          # your pod is eligible to be scheduled based on labels on pods that are
          # already running on the node rather than based on labels on nodes.
          # There are currently two types of anti-affinity:
          #    "requiredDuringSchedulingIgnoredDuringExecution"
          #    "preferredDuringSchedulingIgnoredDuringExecution"
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Feb 27 16:55:16 GMT 2024
    - 12.4K bytes
    - Viewed (0)
  8. manifests/charts/gateways/istio-ingress/values.yaml

          tolerations: []
    
          # Specify the pod anti-affinity that allows you to constrain which nodes
          # your pod is eligible to be scheduled based on labels on pods that are
          # already running on the node rather than based on labels on nodes.
          # There are currently two types of anti-affinity:
          #    "requiredDuringSchedulingIgnoredDuringExecution"
          #    "preferredDuringSchedulingIgnoredDuringExecution"
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Feb 27 16:55:16 GMT 2024
    - 13K bytes
    - Viewed (0)
Back to top