Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 8 of 8 for Liveness (0.14 sec)

  1. docs/orchestration/kubernetes/README.md

    ## Monitoring MinIO in Kubernetes
    
    MinIO server exposes un-authenticated liveness endpoints so Kubernetes can natively identify unhealthy MinIO containers. MinIO also exposes Prometheus compatible data on a different endpoint to enable Prometheus users to natively monitor their MinIO deployments.
    
    ## Explore Further
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Aug 12 18:20:36 UTC 2025
    - 1.6K bytes
    - Viewed (0)
  2. cmd/bucket-targets.go

    	Scheme          string
    	Online          bool
    	lastOnline      time.Time
    	lastHCAt        time.Time
    	offlineDuration time.Duration
    	latency         latencyStat
    }
    
    // isOffline returns current liveness result of remote target. Add endpoint to
    // healthCheck map if missing and default to online status
    func (sys *BucketTargetSys) isOffline(ep *url.URL) bool {
    	sys.hMutex.RLock()
    	defer sys.hMutex.RUnlock()
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Fri Aug 29 02:39:48 UTC 2025
    - 20.9K bytes
    - Viewed (0)
  3. cmd/http-tracer.go

    	op = strings.Replace(op, "ClusterCheckHandler", "health.Cluster", 1)
    	op = strings.Replace(op, "ClusterReadCheckHandler", "health.ClusterRead", 1)
    	op = strings.Replace(op, "LivenessCheckHandler", "health.Liveness", 1)
    	op = strings.Replace(op, "ReadinessCheckHandler", "health.Readiness", 1)
    	op = strings.Replace(op, "-fm", "", 1)
    	return op
    }
    
    // If trace is enabled, execute the request if it is traced by other handlers
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Sep 24 17:13:00 UTC 2024
    - 6K bytes
    - Viewed (0)
  4. CHANGELOG/CHANGELOG-1.16.md

    - Adds `\livez` for liveness health checking for kube-apiserver. Using the parameter `--maximum-startup-sequence-duration` will allow the liveness endpoint to defer boot-sequence failures for the specified duration period. ([#81969](https://github.com/kubernetes/kubernetes/pull/81969), [@logicalhan](https://github.com/logicalhan))
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Wed Oct 23 20:13:20 UTC 2024
    - 345.2K bytes
    - Viewed (0)
  5. CHANGELOG/CHANGELOG-1.32.md

    - kubeadm: switched the kube-scheduler static Pod to use the endpoints `/livez` (for startup and liveness probes) and `/readyz` (for the readiness probe). Previously, `/healthz` was used for all probes, which is deprecated behavior in the scope of this component. ([#126945](https://github.com/kubernetes/kubernetes/pull/126945), [@liangyuanpeng](http...
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Wed Aug 13 14:49:49 UTC 2025
    - 412.3K bytes
    - Viewed (0)
  6. CHANGELOG/CHANGELOG-1.34.md

    - Kubeadm: made the coredns deployment manifest use named ports consistently for the liveness and readiness probes. ([#131587](https://github.com/kubernetes/kubernetes/pull/131587), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle]
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Wed Aug 27 10:36:10 UTC 2025
    - 292.8K bytes
    - Viewed (0)
  7. CHANGELOG/CHANGELOG-1.31.md

    - Kubeadm: Switched to using the new etcd endpoints introduced in 3.5.11 - /livez (for liveness probe) and /readyz (for readyness and startup probe). With this change it is no longer possible to deploy a custom etcd version older than 3.5.11 with kubeadm 1.31. If so, please upgrade etcd to a supported version. ([#124465](https://github.com...
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Wed Aug 13 19:49:57 UTC 2025
    - 429.6K bytes
    - Viewed (0)
  8. CREDITS

         communicate, and translate a Work;
     ii. moral rights retained by the original author(s) and/or performer(s);
    iii. publicity and privacy rights pertaining to a person's image or
         likeness depicted in a Work;
     iv. rights protecting against unfair competition in regards to a Work,
         subject to the limitations in paragraph 4(a), below;
      v. rights protecting the extraction, dissemination, use and reuse of data
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Thu Mar 13 05:29:51 UTC 2025
    - 1.8M bytes
    - Viewed (0)
Back to top