- Sort Score
- Result 10 results
- Languages All
Results 1 - 6 of 6 for have (0.14 sec)
-
manifests/charts/istio-control/istio-discovery/values.yaml
# then two meshes must have different Mesh IDs: # - Meshes will have their telemetry aggregated in one place # - Meshes will be federated together # - Policy will be written referencing one mesh from the other # # If an administrator expects that any of these conditions may become true in # the future, they should ensure their meshes have different Mesh IDs # assigned. #
Others - Registered: Wed Mar 20 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 16:58:23 GMT 2024 - 19.6K bytes - Viewed (0) -
manifests/charts/istiod-remote/values.yaml
# then two meshes must have different Mesh IDs: # - Meshes will have their telemetry aggregated in one place # - Meshes will be federated together # - Policy will be written referencing one mesh from the other # # If an administrator expects that any of these conditions may become true in # the future, they should ensure their meshes have different Mesh IDs # assigned. #
Others - Registered: Wed Mar 20 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 16:58:23 GMT 2024 - 19.6K bytes - Viewed (0) -
manifests/charts/istio-cni/values.yaml
# This is only capable of identifying broken pods; the user is responsible for fixing them (generally, by deleting them). # Note this gives the DaemonSet a relatively high privilege, as modifying pod metadata/status can have wider impacts. labelPods: false # deletePods will delete any broken pod. These will then be rescheduled, hopefully onto a node that is fully ready.
Others - Registered: Wed Mar 20 22:53:08 GMT 2024 - Last Modified: Wed Feb 28 17:29:38 GMT 2024 - 5.1K bytes - Viewed (1) -
manifests/charts/gateways/istio-egress/values.yaml
# then two meshes must have different Mesh IDs: # - Meshes will have their telemetry aggregated in one place # - Meshes will be federated together # - Policy will be written referencing one mesh from the other # # If an administrator expects that any of these conditions may become true in # the future, they should ensure their meshes have different Mesh IDs # assigned. #
Others - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Tue Feb 27 16:55:16 GMT 2024 - 12.4K bytes - Viewed (0) -
manifests/charts/gateways/istio-ingress/values.yaml
# then two meshes must have different Mesh IDs: # - Meshes will have their telemetry aggregated in one place # - Meshes will be federated together # - Policy will be written referencing one mesh from the other # # If an administrator expects that any of these conditions may become true in # the future, they should ensure their meshes have different Mesh IDs # assigned. #
Others - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Tue Feb 27 16:55:16 GMT 2024 - 13K bytes - Viewed (0) -
helm/minio/values.yaml
## Node labels for pod assignment ## Ref: https://kubernetes.io/docs/user-guide/node-selection/ ## nodeSelector: {} tolerations: [] affinity: {} topologySpreadConstraints: [] ## Add stateful containers to have security context, if enabled MinIO will run as this ## user and group NOTE: securityContext is only enabled if persistence.enabled=true securityContext: enabled: true runAsUser: 1000 runAsGroup: 1000
Others - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Sun Apr 28 10:14:37 GMT 2024 - 18.4K bytes - Viewed (0)