When you attach a cluster to Containership Cloud, a new
containership-core is created. Workloads are launched in this namespace, that allow you to control your cluster, in the Containership Cloud UI. New Custom Resource Definitions are also created, in order to synchronize the state of your cluster.
The following is an overview of each resource. Generally, you should not update any of these resources. There are safeguards in place on some of these resources, that will overwrite modifications, if they would result in cluster instability (for example, deleting a secret that a core service requires, in order to connect to your API server).
The following workloads are launched on clusters, when attached to Containership Cloud:
deploymentis required for synchronizing Hitachi Kubernetes Service resources with attached Kubernetes clusters. Some examples of resources synchronized and managed by the Coordinator include plugins and secrets added through the UI.
deploymentis used to forward Kubernetes events, relating only to service-managed resources, back to Containership Cloud for health monitoring purposes.
DaemonSetenables some features that require node-level interaction such as synchronizing SSH keys, and registries.
prometheus-prometheus: If you choose to enable the Metrics Collection plugin, these workloads run
Podsto support the Prometheus Operator . They are used to collect, and aggregate
podmetrics, and populate graphs in the Cloud UI.
Custom Resource Definitions (CRDs)
plugins.containership.io: This is used to support syncing the state of plugins installed on your
nodes, such as Metrics Collection, and Log Collection.
registries.containership.io: This is used to support syncing registry credentials added in the Cloud UI, to your
users.containership.io: This is used to support syncing user data (such as SSH keys) on your Containership Cloud account, to each
nodein your cluster.