mountPath: /var/run/secrets/kubernetes. TerminationMessagePath: /dev/termination-log name: TEAMCITY_KUBERNETES_INSTANCE_NAME name: TEAMCITY_KUBERNETES_CLOUD_PROFILE_ID Value: - name: TEAMCITY_KUBERNETES_IMAGE_NAME I don't know if all of the stuff in the spec needs to be in there, but here is what I have. This would be a great use case for running agents inside a cluster. So I need to use one of these options but I'm not sure how to enable either of these two solutions in Kubernetes.ĭoes the TeamCity Kubernetes plugin support the scenario I'm looking for? Has anyone achieved it and how? I was hoping this would be a supported scenario and one I could easily deploy. I want to be able to run Docker in a container, or Docker in Docker. The first uses volume mappings and the second one says start the container using the -privileged flat. The docs on Docker Hub for the jetbrains/teamcity-agent image says, " In a Linux container, if you need a Docker daemon available inside your builds, you have two options:".
This is because the Docker daemon is not running inside the container running in Kubernetes. However, when I try running a simple build command `docker version` I get an error "Cannot connect to the Docker daemon at unix:///var/run/docker.sock". Now, however, I want to be able to run build steps using the Docker runner. The TeamCity Server connected the agents and they are available to my project. I was able to deploy 3 agents into my Kubernetes cluster using the jetbrains/teamcity-agent image. For more information including a complete list of kubectl operations, see the kubectl reference documentation. You can use kubectl to deploy applications, inspect and manage cluster resources, and view logs. I installed the TeamCity Kubernetes Support Plugin and configured the Kubernetes Cloud Profile. kubectl The Kubernetes command-line tool, kubectl, allows you to run commands against Kubernetes clusters.
0 kommentar(er)
