Open the settings of the required project and, under the Cloud Profiles section, click Create new profile.įor general cloud profile options, refer to the Agent Cloud Profile article.

To establish the integration with Kubernetes, you need to create a dedicated cloud profile in TeamCity. # if you use OIDC/Certificate auth strategies # proper RoleBinding subject depends on your Authentication strategy Here is an example of setting up all required permissions via Kubernetes RBAC: Usability: A well-designed interface makes the build process much easier. In fact, there are integrations with Jenkins, Bamboo, and TeamCity, as well as a large number of popular tools and frameworks. Namespaces: get, list - to allow TeamCity to suggest the namespaces available on your server. BrowserStack offers integrations with a wide range of CI/CD tools so as to make developers’ lives easier. You might also require to configure the following privileges for your Kubernetes user role:ĭeployments: list, get - if you want to create an agent pod using a deployment configuration. Make sure the TeamCity user is allowed to perform writing operations in the Kubernetes namespace used by TeamCity agents. TeamCity integration with Kubernetes does not depend on the kubectl tool and thus does not require installing it in your cluster. Refer to our upgrade notes for more details. If you were using the Helm build runner, included in the external Kubernetes Support plugin, note that the built-in integration does not comprise the Helm runner.

Thanks to the Kubernetes Support plugin, TeamCity can run build agents in your Kubernetes cluster.

Download teamcity kubernetes