We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Like gefyra-bridge the gefyra-run cmd should (optionally!) probe the local container with probe-details from pod.
gefyra-unbridge should (optionally!) wait for probes on original container to start responding. This is to ensure that original pod is up and running.
User currently needs to implement this probing manually in some wrapper script. This duplicates probe information and is more error-prone.
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What is the new feature about?
Like gefyra-bridge the gefyra-run cmd should (optionally!) probe the local container with probe-details from pod.
gefyra-unbridge should (optionally!) wait for probes on original container to start responding. This is to ensure that original pod is up and running.
Why would such a feature be important to you?
User currently needs to implement this probing manually in some wrapper script. This duplicates probe information and is more error-prone.
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: