Adding gRPC / polling Tentacles over HTTPS information to existing documentation#3205
Adding gRPC / polling Tentacles over HTTPS information to existing documentation#3205briggs-octo wants to merge 6 commits into
Conversation
|
Pull request environment is available at https://stoctodocspr3205.z22.web.core.windows.net. You can view the ephemeral environment status in Octopus Deploy. This environment will be automatically deprovisioned when the pull request is closed, or after 7 days of inactivity. |
scme0
left a comment
There was a problem hiding this comment.
Approved but I've added a comment to slightly reword the inbound rule description change.
Might be worth confirming the behaviour of Listening Tentacles before merging.
| |---|---|---|---|---|---| | ||
| |HTTP|`TCP 80`|Users|Octopus Server|ALLOW|We recommend only using HTTPS over SSL, however it can be convenient to allow HTTP for the initial connection which is then forced to HTTPS over SSL.| | ||
| |HTTPS|`TCP 443`|Users, Polling Tentacles, external services|Octopus Server|ALLOW|Required for HTTPS over SSL. Also required if using [Polling Tentacles](/docs/infrastructure/deployment-targets/tentacle/tentacle-communication/#polling-tentacles) over [Web Sockets](/docs/infrastructure/deployment-targets/tentacle/windows/polling-tentacles-web-sockets).| | ||
| |HTTPS|`TCP 443`|Users, Polling Tentacles, external services|Octopus Server|ALLOW|Required for HTTPS over SSL. Also required for initial Tentacle registration and if using [Polling Tentacles](/docs/infrastructure/deployment-targets/tentacle/tentacle-communication/#polling-tentacles) over [Web Sockets](/docs/infrastructure/deployment-targets/tentacle/windows/polling-tentacles-web-sockets) or [Polling Tentacles over HTTPS](/docs/infrastructure/deployment-targets/tentacle/polling-tentacles-over-port-443).| |
There was a problem hiding this comment.
| |HTTPS|`TCP 443`|Users, Polling Tentacles, external services|Octopus Server|ALLOW|Required for HTTPS over SSL. Also required for initial Tentacle registration and if using [Polling Tentacles](/docs/infrastructure/deployment-targets/tentacle/tentacle-communication/#polling-tentacles) over [Web Sockets](/docs/infrastructure/deployment-targets/tentacle/windows/polling-tentacles-web-sockets) or [Polling Tentacles over HTTPS](/docs/infrastructure/deployment-targets/tentacle/polling-tentacles-over-port-443).| | |
| |HTTPS|`TCP 443`|Users, Polling Tentacles, external services|Octopus Server|ALLOW|Required for HTTPS over SSL. Also required for initial Tentacle registration if using [Polling Tentacles](/docs/infrastructure/deployment-targets/tentacle/tentacle-communication/#polling-tentacles) over [Web Sockets](/docs/infrastructure/deployment-targets/tentacle/windows/polling-tentacles-web-sockets) or [HTTPS](/docs/infrastructure/deployment-targets/tentacle/polling-tentacles-over-port-443).| |
As far as I'm aware it's not required for Listening Tentacles because you register them on Octopus manually. You need to do this because Octopus generates the thumbprint. It's been a little while since I've setup a listening tentacle though.
Adding gRPC port information, Tentacle registration, and Polling Tentacles over HTTPS to hardening documentation: https://octopus.com/docs/security/hardening-octopus#harden-your-network
Adding Kubernetes Live Object Status to the Octopus Server installation components: https://octopus.com/docs/installation#octopus-components