- Sort Score
- Result 10 results
- Languages All
Results 11 - 18 of 18 for Gillet (0.15 sec)
-
manifests/charts/gateways/istio-egress/templates/injected-deployment.yaml
maxUnavailable: {{ $gateway.rollingMaxUnavailable }} template: metadata: labels: {{ $gateway.labels | toYaml | indent 8 }} {{- if eq .Release.Namespace "istio-system"}} heritage: Tiller release: istio chart: gateways {{- end }} install.operator.istio.io/owning-resource: {{ .Values.ownerName | default "unknown" }} operator.istio.io/component: "EgressGateways"
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 18 18:16:49 GMT 2024 - 5K bytes - Viewed (0) -
common-protos/k8s.io/api/authentication/v1alpha1/generated.proto
// +optional optional k8s.io.apimachinery.pkg.apis.meta.v1.ObjectMeta metadata = 1; // Status is filled in by the server with the user attributes. optional SelfSubjectReviewStatus status = 2; } // SelfSubjectReviewStatus is filled by the kube-apiserver and sent back to a user. message SelfSubjectReviewStatus { // User attributes of the user making this request. // +optional
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 2K bytes - Viewed (0) -
manifests/charts/istiod-remote/values.yaml
# Kubernetes >=v1.11.0 will create two PriorityClass, including system-cluster-critical and # system-node-critical, it is better to configure this in order to make sure your Istio pods # will not be killed because of low priority class. # Refer to https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#priorityclass # for more detail. priorityClassName: "" proxy: image: proxyv2
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) -
common-protos/k8s.io/api/apps/v1/generated.proto
// Example: when this is set to 30%, the new ReplicaSet can be scaled up immediately when // the rolling update starts, such that the total number of old and new pods do not exceed // 130% of desired pods. Once old pods have been killed, // new ReplicaSet can be scaled up further, ensuring that total number of pods running // at any time during the update is at most 130% of desired pods. // +optional
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 34.5K bytes - Viewed (0) -
common-protos/k8s.io/api/extensions/v1beta1/generated.proto
// Example: when this is set to 30%, the new RC can be scaled up immediately when // the rolling update starts, such that the total number of old and new pods do not exceed // 130% of desired pods. Once old pods have been killed, // new RC can be scaled up further, ensuring that total number of pods running // at any time during the update is at most 130% of desired pods. // +optional
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 45.6K bytes - Viewed (0) -
common-protos/k8s.io/api/imagepolicy/v1alpha1/generated.proto
// +optional optional k8s.io.apimachinery.pkg.apis.meta.v1.ObjectMeta metadata = 1; // Spec holds information about the pod being evaluated optional ImageReviewSpec spec = 2; // Status is filled in by the backend and indicates whether the pod should be allowed. // +optional optional ImageReviewStatus status = 3; } // ImageReviewContainerSpec is a description of a container within the pod creation request.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 3.2K bytes - Viewed (0) -
manifests/charts/gateways/istio-egress/templates/deployment.yaml
maxUnavailable: {{ $gateway.rollingMaxUnavailable }} template: metadata: labels: {{ $gateway.labels | toYaml | indent 8 }} {{- if eq .Release.Namespace "istio-system"}} heritage: Tiller release: istio chart: gateways {{- end }} service.istio.io/canonical-name: {{ $gateway.name }}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 18 18:16:49 GMT 2024 - 12.1K bytes - Viewed (0) -
common-protos/k8s.io/api/apps/v1beta1/generated.proto
// Example: when this is set to 30%, the new ReplicaSet can be scaled up immediately when // the rolling update starts, such that the total number of old and new pods do not exceed // 130% of desired pods. Once old pods have been killed, // new ReplicaSet can be scaled up further, ensuring that total number of pods running // at any time during the update is at most 130% of desired pods. // +optional
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 24K bytes - Viewed (0)