Kubernetes Pod Service Account authentication

Octopus has introduced simpler authentication for its Workers running within Kubernetes clusters by utilizing the Kubernetes Pod Service Account's credentials, allowing them to connect back to the parent cluster without needing to send extra credentials from the Octopus Server. This update facilitates the management of clusters by workers deployed as containers in Kubernetes, enhancing scenarios like database backups, schema migrations, and load balancer configurations. A pool of Octopus workers can be created within a Kubernetes cluster by deploying the Tentacle image from Docker Hub or using Octopus Deploy Runbooks, requiring the installation of kubectl on each worker for command execution against Kubernetes clusters. The new authentication mode, Pod Service Account, streamlines adding deployment targets, requiring only the cluster's URL and token file path, thus eliminating the need for storing cluster certificate data on the Octopus Server. This advancement simplifies the deployment processes by ensuring the workers can autonomously manage the clusters they deploy to, leading to more secure and efficient DevOps practices.