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
When pod contains socket-type or exec-type probes (anything other than http-type probes), setprobe.sh is unable to handle. The problem is silently ignored which leads the user to assume probing was successful.
gefyra-run hangs with no error msg
What did you expect to happen?
gefyra-bridge to check probe-types in Carrier._ensure_probes() and error out with "Pod xyz uses non-http-type probes, which is not supported. Please consider option --no-probe-handling."
Please provide the output of gefyra check.
.
How can we reproduce it (as minimally and precisely as possible)?
run gefyra-bridge on any pod which has e.g. an exec-type probe
What Kubernetes setup are you working with?
.
OS version
No response
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered:
What happened?
When pod contains socket-type or exec-type probes (anything other than http-type probes), setprobe.sh is unable to handle. The problem is silently ignored which leads the user to assume probing was successful.
gefyra-run hangs with no error msg
What did you expect to happen?
gefyra-bridge to check probe-types in Carrier._ensure_probes() and error out with "Pod xyz uses non-http-type probes, which is not supported. Please consider option --no-probe-handling."
Please provide the output of
gefyra check
..
How can we reproduce it (as minimally and precisely as possible)?
run gefyra-bridge on any pod which has e.g. an exec-type probe
What Kubernetes setup are you working with?
.
OS version
No response
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: