- image: registry.k8s.io/nginx:1.7.9
    name: target
    readinessProbe:
      exec:
        command: ["/bin/sh", "-c", "cat probe"]
    livenessProbe:
      exec:
        command: ["/bin/sh", "-c", "cat probe"]
    startupProbe:
      exec:
        command: ["/bin/sh", "-c", "cat probe"]
  initContainers:
  - image: busybox

apiVersion: release-notes/v2
kind: feature
area: traffic-management
releaseNotes:
  - |

      Startup probes run only at the start of the pod. Once the startup probe completes, readiness probes will continue.
      
      By using a startup probe, we can poll for the sidecar to start more aggressively, without polling as aggressively throughout
      the entire pod's lifecycle.
      On average, this improves pod startup time by roughly 1s.
      

		// and we don't need to probe the capability.
		probes = probes[:1]
	}
	for i := range probes {
		s, err := sysSocket(syscall.AF_INET6, syscall.SOCK_STREAM, syscall.IPPROTO_TCP)
		if err != nil {
			continue
		}
		defer poll.CloseFunc(s)
		syscall.SetsockoptInt(s, syscall.IPPROTO_IPV6, syscall.IPV6_V6ONLY, probes[i].value)
		sa, err := probes[i].laddr.sockaddr(syscall.AF_INET6)
		if err != nil {

 *
 * When the probe is armed, a probe file is created (or re-created) under the hierarchy.
 * This should cause a file system event to be produced by the operating system.
 * We listen to those events specifically in {@link FileWatcherRegistry}.
 * Once the event arrives, {@link #triggerWatchProbe(String)} is called with the path,
 * and the probe becomes triggered (or proven).
 *

Ralf Pannemans <******@****.***> 1627289097 +0200

John Howard <******@****.***> 1597787025 -0700

"httpQueryParameterName"
"minimumRingSize"
"path"
"tcpKeepalive"
"http1MaxPendingRequests"
"http2MaxRequests"
"maxRequestsPerConnection"
"maxRetries"
"idleTimeout"
"h2UpgradePolicy"
"useClientProtocol"
"probes"
"from"
"to"
"workloadSelector"
"configPatches"
"proxyVersion"
"metadata"
"service"
"vhost"
"gateway"
"filterChain"
"operation"
"value"
"filterClass"
"context"
"proxy"
"listener"

package org.apache.maven.building;

/**
 * Describes a problem that was encountered during settings building. A problem can either be an exception that was
 * thrown or a simple string message. In addition, a problem carries a hint about its source, e.g. the settings file
 * that exhibits the problem.
 *
 */
public interface Problem {

    /**
     * The different severity levels for a problem, in decreasing order.
     */
    enum Severity {

    /**
     * A long description detailing the problem.
     * <p>
     * Details can elaborate on the problem, and provide more information about the problem.
     * They can be multiple lines long, but should not detail solutions; for that, use {@link #getSolutions()}.
     */
    @Nullable
    String getDetails();

    /**
     * Return the location data associated available for this problem.
     */