-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
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
fix: make port 22 in transparent-proxy clear #1490
Conversation
Signed-off-by: Charly Molter <[email protected]>
❌ Deploy Preview for kuma failed.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd change one line mentioned.
@@ -51,11 +51,23 @@ The host that will run the `kuma-dp` process in transparent proxying mode needs | |||
--redirect-dns | |||
``` | |||
|
|||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick:
{% endwarning %} | ||
|
||
The changes will persist over restarts, so this command is needed only once. Reverting to the original state of the host can be done by issuing `kumactl uninstall transparent-proxy`. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick:
{% endwarning %} | ||
|
||
The changes will persist over restarts, so this command is needed only once. Reverting to the original state of the host can be done by issuing `kumactl uninstall transparent-proxy`. | ||
|
||
The changes will persist over restarts, so this command is needed only once. Reverting to the original state of the host can be done by issuing `kumactl uninstall transparent-proxy` {% if_version gte:2.2.x %} (which is not implemented yet see issue [#8071](https://github.com/kumahq/kuma/issues/8071)).{% endif_version %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It only makes sense when you know that we rewrote TP. Why would we mention a command that does not exist.
I'd go with:
The changes will persist over restarts, so this command is needed only once. Reverting to the original state of the host can be done by issuing `kumactl uninstall transparent-proxy` {% if_version gte:2.2.x %} (which is not implemented yet see issue [#8071](https://github.com/kumahq/kuma/issues/8071)).{% endif_version %} | |
The changes will persist over restarts, so this command is needed only once. {% if_version lte:2.1.x %} Reverting to the original state of the host can be done by issuing `kumactl uninstall transparent-proxy`.{% endif_version %}{% if_version gte:2.2.x %} Reverting to the original state of the host is not yet implemented, see issue [#8071](https://github.com/kumahq/kuma/issues/8071).{% endif_version %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait. kumactl install transparent-proxy
needs to be executed after every system reboot or you need to have some solution for iptables rules persistence in place. Otherwise, the transparent proxy configuration won't survive restarts.
{% endwarning %} | ||
|
||
The changes will persist over restarts, so this command is needed only once. Reverting to the original state of the host can be done by issuing `kumactl uninstall transparent-proxy`. | ||
|
||
The changes will persist over restarts, so this command is needed only once. Reverting to the original state of the host can be done by issuing `kumactl uninstall transparent-proxy` {% if_version gte:2.2.x %} (which is not implemented yet see issue [#8071](https://github.com/kumahq/kuma/issues/8071)).{% endif_version %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait. kumactl install transparent-proxy
needs to be executed after every system reboot or you need to have some solution for iptables rules persistence in place. Otherwise, the transparent proxy configuration won't survive restarts.
<Explain your change!>
Did you sign your commit? Instructions
Have you read Contributing guidelines?