Darwin Information Typing Architecture
Open project settings and navigate to the tab-name settings tab. Open configuration settings and navigate to the configuration-tab-name settings tab.
Open the tab-name settings tab and click the button-name button.
Click Add Connection. Note that connections can be used only in their parent projects and their subprojects. If you want a connection to be available globally, add it to the Root project.
Select "connection-type" in the Connection Type drop-down menu. Ensure the Enable unique callback URL setting is enabled to generate a unique ID added to your callback URL. This setting bolsters the security of your setup by mitigating the risk of mix-up attacks: attacks utilizing malicious authorization servers that impersonate real auth servers to trick a victim client into leaking an authorization code (token). Using the unique-url-sample
URL format ensures an attacker cannot hand-craft an address acknowledged by TeamCity.
note
Whenever you toggle this setting on or off, the callback URL changes. Update OAuth settings on the VCS side accordingly.
IDs are unique for every connection, including copies of existing connections. If you clone a connection with this setting enabled, remember to update your VCS OAuth settings.
Click Test connection to verify TeamCity can access your resources, and save your new connection.
Refreshable access tokens are short-lived tokens acquired by TeamCity from a required VCS provider via existing OAuth connections (as opposed to static PAT tokens issued manually by users on a VCS hosting side). See the following article for more information on generating and using refreshable tokens: Manage Refreshable Access Tokens.
Specify the URL of the Kubernetes API server.
Enter the content of the CA certificate for your cluster.
Specify a required Kubernetes namespace. Leave empty to use the default namespace.
Select the required authentication strategy. Depending on the selected strategy, the set of additional options will vary. Refer to the Kubernetes documentation for details on available options.
note
The Token strategy accepts any token types supported by Kubernetes.
note
docker-feature-name is a part of the TeamCity-Docker/Podman integration toolset. Refer to this documentation article for information on software requirements, supported environments, and other common aspects of this integration: Integrating TeamCity with Container Managers.
warning
TeamCity will drop support for Java versions older than 21 in one of the future versions. If you're using a non-bundled Java 21, we strongly recommend upgrading to a newer version.