Search Options

Results per page
Sort
Preferred Languages
Advance

Results 11 - 20 of 20 for Readiness (0.45 sec)

  1. cni/pkg/nodeagent/healthServer.go

    package nodeagent
    
    import (
    	"net/http"
    	"sync/atomic"
    
    	"istio.io/istio/cni/pkg/constants"
    )
    
    // StartHealthServer initializes and starts a web server that exposes liveness and readiness endpoints at port 8000.
    func StartHealthServer() (installReady *atomic.Value, watchReady *atomic.Value) {
    	router := http.NewServeMux()
    	installReady, watchReady = initRouter(router)
    
    	go func() {
    Go
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Apr 15 01:29:35 GMT 2024
    - 1.8K bytes
    - Viewed (0)
  2. operator/cmd/mesh/testdata/manifest-generate/data-snapshot.tar.gz

    privileged securityContext privileged: false # The number of successive failed probes before indicating readiness failure. readinessFailureThre: 4 # The initial delay for readiness probes in seconds. readinessInitialDela: 0 # The period between readiness probes. readinessPeriodSecon: 15 # Enables or disables a startup probe. # For optimal startup times, changing this should be tied to the readiness probe values. # # If the probe is enabled, it is recommended to have delay=0s,period=15s,failureThreshold=4....
    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. 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)
  4. 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)
  5. manifests/charts/istiod-remote/templates/crd-all.gen.yaml

                        - port
                        type: object
                      initialDelaySeconds:
                        description: Number of seconds after the container has started
                          before readiness probes are initiated.
                        format: int32
                        type: integer
                      periodSeconds:
                        description: How often (in seconds) to perform the probe.
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Apr 22 20:20:47 GMT 2024
    - 606.1K bytes
    - Viewed (0)
  6. manifests/charts/base/crds/crd-all.gen.yaml

                        - port
                        type: object
                      initialDelaySeconds:
                        description: Number of seconds after the container has started
                          before readiness probes are initiated.
                        format: int32
                        type: integer
                      periodSeconds:
                        description: How often (in seconds) to perform the probe.
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Apr 22 20:20:47 GMT 2024
    - 606.1K bytes
    - Viewed (0)
  7. 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)
  8. 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)
  9. cni/pkg/cmd/root.go

    			}
    
    			ambientAgent.Start()
    			defer ambientAgent.Stop()
    
    			log.Info("Ambient node agent started, starting installer...")
    
    		} else {
    			// Ambient not enabled, so this readiness flag is no-op'd
    			watchServerReady.Store(true)
    		}
    
    		installer := install.NewInstaller(&cfg.InstallConfig, installDaemonReady)
    
    		repair.StartRepair(ctx, cfg.RepairConfig)
    
    Go
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Apr 30 22:24:38 GMT 2024
    - 12.5K bytes
    - Viewed (0)
  10. 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)
Back to top