The Kubernetes-native platform (v2).
The Package manager for Kubernetes.
The Kubernetes-native Service Broker.
An application services requests and background jobs for a deployed git repository. Each application includes a set of Containers used to run isolated processes, and a Release that defines the current Build and Config deployed by containers.
Drycc builds are created automatically on the controller when a developer uses
git push drycc master. When a new build is created, a new Release is created automatically.
Config refers to a set of environment variables used by Containers in as Application.
When Config is changed, a new Release is created automatically.
Drycc containers are instances of Docker containers used to run Applications. Containers perform the actual work of an Application by servicing requests or by running background tasks as part of the cluster.
Each container gets its own ephemeral filesystem, with a fresh copy of the most recently deployed code. During the container’s lifetime, its running processes can use the filesystem as a temporary scratchpad, but no files that are written are visible to processes in any other container. Any files written to the ephemeral filesystem will be discarded the moment the container is either stopped or restarted.
There are several states that a container can be in at any time. The states are:
The controller is the "brain" of the Drycc platform. A controller manages Applications and their lifecycle.
The controller is in charge of:
The Controller stack includes:
Drycc keys are SSH Keys used during the git push process. Each user can use the client to manage a list of keys on the Controller.
A Drycc release is a combination of a Build with a Config. Each Application is associated with one release at a time. Drycc releases are numbered and new releases always increment by one (e.g. v1, v2, v3).
Containers that host an application use these release versions to pull the correct code and configuration.
The Scheduler is responsible for creating, starting, stopping, and destroying Containers. For example, a command such as
drycc scale cmd=10 tells the Scheduler to run ten Containers from the Docker image for your Application.
The Scheduler must decide which machines are eligible to run these container jobs. Scheduler backends vary in the details of their job allocation policies and whether or not they are resource-aware, among other features.
The Drycc scheduler client is implemented in the Controller component.
A Kubernetes Service is an abstraction which defines a logical set of Pods and a policy by which to access them. In Workflow, a Service is used to load-balance an application's Containers internally through a virtual IP address.