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
{{ message }}
This repository has been archived by the owner on Jan 18, 2023. It is now read-only.
operator.md states "You can also set the argument --insecure to false and the webhook service will revert back to regular TLS". However, webhook.py uses mutual tls when self.insecure == "False".
Therefore, whilst operator.md is factually accurate because "false"!="False", it is perhaps a little bit misleading (it certainly confused me)!
My proposal is to update operator.md so that is states "You can also set the argument --insecure to True and the webhook service will revert back to regular TLS"
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
operator.md states "You can also set the argument --insecure to false and the webhook service will revert back to regular TLS". However, webhook.py uses mutual tls when self.insecure == "False".
Therefore, whilst operator.md is factually accurate because "false"!="False", it is perhaps a little bit misleading (it certainly confused me)!
My proposal is to update operator.md so that is states "You can also set the argument --insecure to True and the webhook service will revert back to regular TLS"
The text was updated successfully, but these errors were encountered: