Octopus Tentacle Image - Githubissues

Related Issue

Creates an initial Tentacle Dockerfile that can be built through our GH actions.
The image will work as either:
- Deployment Target: With Octopus Deploy, you can deploy software to Windows servers, Linux servers, Microsoft Azure, AWS, Kubernetes clusters, cloud regions, or an offline package drop. Regardless of where you’re deploying your software, these machines and services are known as your deployment targets.
- Worker: Workers are machines that can execute tasks that don’t need to be run on the Octopus Server or individual deployment targets.

This page has useful information about Deployment target licensing
This page has information on how to run this image as a Deployment Target or a Worker.
Will need to create an API key
Seems like the internal port will need to be 10933
I'm not sure if setting TargetWorkerPool to a value that doesn't exist will create a pool or if it needs to be set to a value predefined in Octopus.

I built the image and did a test run and was able to register the tentacle with our OctopusDeploy instance.

[ ] Consult the results of the terraform-plan job inside the "Terraform Checks" workflow run for this PR. Confirm that there are no unexpected changes!

[ ] Changes with security implications have been approved by a security engineer (changes to authentication, encryption, handling of PII, etc.)
[ ] Any dependencies introduced have been vetted and discussed

[ ] Oncall has been notified if this change is going in after-hours
[ ] If there are changes that cannot be tested locally, this has been deployed to our Azure dev environment for verification.