This content is associated with a legacy version of the Replicated product. For the current Replicated product documentation, see docs.replicated.com.
The Replicated Kubernetes installer builds on kubeadm, adding support for Pod networking, relocatable Persistent Volumes, and Ingress.
Replicated’s install script will first install Docker and a few binaries on the host:
kubelet binary runs as a systemd service, while
kubectl commands are run manually.
Replicated then delegates to
kubeadm init to bootstrap the cluster.
All system services besides
kubelet run as pods in the
kube-system namespace, including the Kubernetes API Server, Kube Proxy, Etcd, Kube Controller Manager, the Kube Scheduler, and CoreDNS.
Replicated adds a Weave DaemonSet to the
kube-system namespace to provide pod networking on every node in the cluster.
Weave places a binary in
/opt/cni/bin that fulfills the CNI interface, which ensures that every pod is assigned an IP address that is routeable across the cluster.
The Weave DaemonSet includes a Network Policy Controller to support NetworkPolicy resources in the cluster.
All traffic between hosts is encrypted by default.
Replicated installs the Rook Operator in the
rook-ceph-system namespace, which manages the ceph storage system.
Replicated creates a Ceph cluster by creating a Cluster config in the
rook-ceph namespace and configures the cluster to use the
/opt/replicated/rook directory on all nodes automatically.
A Pool is created to provide block storage backed by the cluster for PersistentVolumeClaims.
Replicated will automatically increase the replication level of this Pool as nodes are added to the cluster, up to a maximum replication factor of 3.
Previous versions of Replicated were bundled with Rook version 0.8. When upgrading Replicated the Rook Operator will not be upgraded to the current version. Manual steps can be followed using this guide.
After a Kubernetes cluster has been brought up, a Deployment is created in the default namespace for Replicated. When a license is uploaded, Replicated will generate a namespace for the application and apply the release yaml to it. There are a few cases in which Replicated will directly modify application config yaml:
- If running in airgap mode, all Pod images will be rewritten to pull from the registry running in the Replicated daemon pod.
- If a pod mounts a Persistent Volume that is included in snapshots, Replicated will add a sidecar to the pod to backup the contents.
- All PersistentVolumeClaims will receive the
storageClassNameproperty to ensure they are automatically provisioned by Rook.
- All Deployments, ReplicaSets, ReplicationControllers and StatefulSets without the
replicasproperty explicitly set will implicitly scale to 1 replica when started.
- All Pods that use the Ceph Shared Filesystem will have an initContainer injected to verify the mount.