#Teamcity kubernetes how to#

As nodes are removed from the cluster, those Pods are garbage collected. As nodes are added to the cluster, Pods are added to them. Example of ReplicasSets? apiVersion: apps/v1Ī DaemonSet ensures that all (or some) Nodes run a copy of a Pod. If there is a Pod that has no OwnerReference or the OwnerReference is not a Controller and it matches a ReplicaSet’s selector, it will be immediately acquired by said ReplicaSetģ. It’s through this link that the ReplicaSet knows of the state of the Pods it is maintaining and plans accordingly.Ī ReplicaSet identifies new Pods to acquire by using its selector. All Pods acquired by a ReplicaSet have their owning ReplicaSet’s identifying information within their ownerReferences field. When a ReplicaSet needs to create new Pods, it uses its Pod template.Ī ReplicaSet is linked to its Pods via the Pods’ metadata.ownerReferences field, which specifies what resource the current object is owned by. A ReplicaSet then fulfills its purpose by creating and deleting Pods as needed to reach the desired number.

#Teamcity kubernetes how to#

The ReplicaSet ensures that a specified number of Pod replicas are running at any time.Ī ReplicaSet is defined with fields, including a selector that specifies how to identify Pods it can acquire, a number of replicas indicating how many Pods it should be maintaining, and a pod template specifying the data of new Pods it should create to meet the number of replicas criteria. It uses a template that describes what each Pod must contain. Deployments can also be scaled.Ī ReplicaSet is a set of Pod templates that describes a set of Pod replicas.

Each deployment revision can also be rolled back. During a rollout, the deployment controller changes the actual state to the state that you want at a controlled rate. When you revise a deployment, a ReplicaSet is created that describes the state that you want. You can define a deployment to create a ReplicaSet or to remove deployments and adopt all their resources with new deployments. A ReplicaSet ensures that a specified number of Pod replicas are running continuously and helps with load-balancing in case of an increase in resource usage. ReplicaSet helps bring up a new instance of a Pod when the existing one fails, scale it up when the running instances are not up to the specified number, and scale down or delete Pods if another instance with the same label is created. Its purpose is to maintain the specified number of Pod instances running in a cluster at any given time to prevent users from losing access to their application when a Pod fails or is inaccessible. Has anyone encountered this before? Sounds like a problem with how TeamCity tries to figure out how much disk space it has left, but I don't know how to approach this and I couldn't find something online.A ReplicaSet is a process that runs multiple instances of a Pod and keeps the specified number of Pods constant. This causes some unnecessary annoying warnings but it also pauses the build queue automatically, which means I have to login and unpause the queue manually eveytime I want to run a build. However, TeamCity insists that there is no disk space available. I can see that because all the files and folders are correctly written on the host. The Docker images of both TeamCity server and agent are configured correctly in terms of their volumes.

TeamCity agent 47175 (same build as the server I suppose).

Please contact your system administrator. However, there is enough disk space and if I ignore these warnings, everything works fine.įor example this is the message of TeamCity server: Warning: Low disk space for the directory: '/data/teamcity_server/datadir/system'.ĭisk space available: 0 B which is below the limit of 500 MB. They both report that they have zero disk space available.

I have a strange problem with TeamCity server (and TeamCity agent).