You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Read health checks config after target resource is fetched.
Check if it will be possible for the app to steal health checks (e.g incoming config does not exclude health checks port and no http filter is used) and warn the user (warning should be dismissable from the IDE). This should help most new users, who don't use advanced configuration.
At runtime, detect when the app subscribes to health check port without an HTTP filter and issue a warning from within the intproxy. This should help us when reading logs.
Based on k8s docs, we can have exec, httpGet, tcpSocket and grpc probes:
exec probes we should probably ignore, because the command can do anything
tcpSocket probes can definitely be ignored, because the connection will always be accepted (either by target container or by the agent)
httpGet - we have to check port+headers+path against steal configuration
grpc - we can infer the path from configured service name and compare port+path against steal configuration
We should inspect both liveness and readiness probes
The text was updated successfully, but these errors were encountered:
We can:
Based on k8s docs, we can have
exec
,httpGet
,tcpSocket
andgrpc
probes:exec
probes we should probably ignore, because the command can do anythingtcpSocket
probes can definitely be ignored, because the connection will always be accepted (either by target container or by the agent)httpGet
- we have to check port+headers+path against steal configurationgrpc
- we can infer the path from configured service name and compare port+path against steal configurationThe text was updated successfully, but these errors were encountered: