- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 34 for Readiness (0.22 sec)
-
docs/metrics/healthcheck/README.md
scheme: HTTP initialDelaySeconds: 120 periodSeconds: 30 timeoutSeconds: 10 successThreshold: 1 failureThreshold: 3 ``` ## Readiness probe This probe always responds with '200 OK'. Only fails if 'etcd' is configured and unreachable. When readiness probe fails, Kubernetes like platforms turn-off routing to the container. ``` readinessProbe: httpGet: path: /minio/health/ready port: 9000
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jul 06 16:18:38 GMT 2023 - 2.5K bytes - Viewed (0) -
architecture/environments/operator.md
resources | [resources](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#resource-requests-and-limits-of-pod-and-container) readinessProbe | [readiness probes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/) replicaCount | [replica count](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/)
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Aug 09 22:09:18 GMT 2023 - 13.4K bytes - Viewed (0) -
operator/README.md
- [resources](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#resource-requests-and-limits-of-pod-and-container) - [readiness probes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/) - [replica count](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/)
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Sun Sep 17 08:27:52 GMT 2023 - 17.5K bytes - Viewed (0) -
docs/config/README.md
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Sep 11 21:48:54 GMT 2023 - 17.7K bytes - Viewed (0) -
common-protos/k8s.io/api/discovery/v1/generated.proto
// indicates an unknown state. In most cases consumers should interpret this // unknown state as ready. For compatibility reasons, ready should never be // "true" for terminating endpoints, except when the normal readiness // behavior is being explicitly overridden, for example when the associated // Service has set the publishNotReadyAddresses flag. // +optional optional bool ready = 1;
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 8K bytes - Viewed (0) -
cni/README.md
- the program inserts `CNI_NETWORK_CONFIG` into the `plugins` list in `/etc/cni/net.d/${CNI_CONF_NAME}` - the actual code is in pkg/install - including a readiness probe, monitoring. - it also sets up a UDS socket for istio-cni to send logs to this container.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri May 03 19:29:42 GMT 2024 - 12.3K bytes - Viewed (0) -
common-protos/k8s.io/api/core/v1/generated.proto
// +optional optional PodDNSConfig dnsConfig = 26; // If specified, all readiness gates will be evaluated for pod readiness. // A pod is ready when all its containers are ready AND // all conditions specified in the readiness gates have status equal to "True" // More info: https://git.k8s.io/enhancements/keps/sig-network/580-pod-readiness-gates // +optional repeated PodReadinessGate readinessGates = 28;
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 255.8K bytes - Viewed (0) -
common-protos/k8s.io/api/apps/v1/generated.proto
// pod is immediatedly created on that node without considering surge limits. // Allowing surge implies the possibility that the resources consumed by the // daemonset on any given node can double if the readiness check fails, and // so resource intensive daemonsets should take into account that they may // cause evictions during disruption. // +optional optional k8s.io.apimachinery.pkg.util.intstr.IntOrString maxSurge = 2;
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
// pod is immediatedly created on that node without considering surge limits. // Allowing surge implies the possibility that the resources consumed by the // daemonset on any given node can double if the readiness check fails, and // so resource intensive daemonsets should take into account that they may // cause evictions during disruption. // This is an alpha field and requires enabling DaemonSetUpdateSurge feature gate.
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/apps/v1beta2/generated.proto
// pod is immediatedly created on that node without considering surge limits. // Allowing surge implies the possibility that the resources consumed by the // daemonset on any given node can double if the readiness check fails, and // so resource intensive daemonsets should take into account that they may // cause evictions during disruption. // +optional optional k8s.io.apimachinery.pkg.util.intstr.IntOrString maxSurge = 2;
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 36.4K bytes - Viewed (0)