Cluster defines any runtime for running containers, in the broadest sense of the word “runtime”.
ClusterSpec defines how to find the cluster we’re running containers on.
Tilt currently supports connecting to an existing Kubernetes cluster or an existing Docker Daemon (for Docker Compose).
Connection spec for an existing cluster.
Defines connection to a Docker daemon.
The docker host to use.
If not specified, will read the DOCKER_HOST env or use the default docker host.
Defines connection to a Kubernetes cluster.
The name of the kubeconfig context to use.
If not specified, will use the default context in the kubeconfig.
The default namespace to use.
If not specified, will use the namespace in the kubeconfig.
ClusterStatus defines the observed state of Cluster
The preferred chip architecture of the cluster.
On Kubernetes, this will correspond to the kubernetes.io/arch annotation on a node.
On Docker, this will be the Architecture of the Docker daemon.
Note that many clusters support multiple chipsets. This field doesn’t intend that this is the only architecture a cluster supports, only that it’s one of the architectures.
ConnectedAt indicates the time at which the cluster connection was established.
Consumers can use this to detect when the underlying config has changed and refresh their client/connection accordingly.
An unrecoverable error connecting to the cluster.