Default Service Account authentication strategy is not available for Kubernetes Cloud Profile

Question

Confirmed affected versions: 2025.03 and later

The Default Service Account authentication strategy is no longer available when creating a Kubernetes Cloud Profile. Is it possible to re-enable it, as it was in earlier versions of TeamCity?

Answer

The following internal property can be used to re-enable the Default Service Account authentication strategy for Kubernetes Cloud Profile:

teamcity.kubernetes.localServiceAccount.enable=true

Important notes

• The Default Service Account authentication strategy was disabled for security reasons. Re-enabling it is not recommended, as it will represent a security risk.
• These internal properties were proven to work in the 2025.03 version of TeamCity. This may change in future versions.

Additional information

Enabling the Default Credential Provider Chain authentication for AWS, Amazon EKS, Amazon ECR connections