OSM implicitly overwrites the timeouts of kubernetes probes

[davinci26]

Bug description:

Assume that I have a pod where:

           livenessProbe:
            initialDelaySeconds: 1
            timeoutSeconds: 30

Then the timeout will be overwritten by the the Envoy cluster connect timeout and the route/httpconnection manager. So, this behavior overwrites the value the user sets implicitly.

As discussed offline we can fix this by propagating the probe value to the envoy route config and remove the connect_timeout in the cluster config.

Affected area (please mark with X where applicable):

• Install [ ]
• SMI Traffic Access Policy [ ]
• SMI Traffic Specs Policy [ ]
• SMI Traffic Split Policy [ ]
• Permissive Traffic Policy [ ]
• Ingress [ ]
• Egress [ ]
• Envoy Control Plane [x]
• CLI Tool [ ]
• Metrics [ ]
• Certificate Management [ ]
• Sidecar Injection [ ]
• Logging [ ]
• Debugging [ ]
• Tests [ ]
• Demo [ ]
• CI System [ ]

Expected behavior:

Steps to reproduce the bug (as precisely as possible):

How was OSM installed?:

Anything else we need to know?:

Bug report archive:

Environment:

• OSM version (use osm version):
• Kubernetes version (use kubectl version):
• Size of cluster (number of worker nodes in the cluster):
• Others:

[davinci26]

This affects Windows demo so I will take it before I can merge #4059