4.0.0-505

Auto-configuration of all cluster information now possible

This version changes the plugin's default behavior to reduce configuration requirements when the server itself is deployed to Kubernetes, and agent pods are being created in the same cluster as the server.

Most configuration fields in Cluster Profile > Cluster Information are now optional, and the plugin supports auto-refreshing of ephemeral bound service account tokens for the server pod, rather than relying on a long-lived service account token.

For now, users will still need to use long-lived tokens if running their server outside Kubernetes, or creating agents in a different cluster to the GoCD server. If this is a use case you'd like to address, please raise an issue.

If you meet the requirements from the documentation, you should be able to remove your configuration values for all or some of Cluster URL, Namespace, Security Token & CA Certificate Data and rely on Kubernetes defaults.

Breaking Changes

As a side-effect of this, there is a change in the behaviour for the namespace field in some limited cases.

You should ensure your Cluster Profiles have the namespace deliberately set to default if:

• any existing cluster profiles do not have namespace set but expect agent pods to be created in the default namespace
• and you run your GoCD server in a Kubernetes pod outside the default namespace
• and have a service account attached to the pod, with auto-mounted service tokens (as is default with the GoCD Helm Chart)

If any of these are not true, you are not affected and can ignore this.

Changelog v3.9.1-501..f4dfc72

70b7882 - Change cluster URL and security tokens to be optional, defaulting to that mounted into the pod
9466554 - Support use of EC keys to secure cluster API servers
c737e63 - Clarify token permissions

SHA256 Checksums

56838ecb2b4bd66779e3b0720b8deeb056539695781441347d55603e2b2705ea *kubernetes-elastic-agent-4.0.0-505.jar