Lobs communication spike #947
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This is a POC to evaluate ways of handling communication between processes for live kubernetes object status
Includes changes from main...robe/reverse-tentacle
Octopus Server side: https://github.com/OctopusDeploy/OctopusDeploy/compare/robe/reverse-tentacle
What it does
Example with simple Go App hitting the gRPC service in Tentacle all running in a cluster
Top left terminal is the Go App's pod logs, top right terminal is Tentacles pod logs and bottom terminal is Octopus server's logs
Screen.Recording.2024-05-27.at.4.05.04.pm.mov
Go app