Cluster

All services present in Cluster.

You can get information about your Cluster:

  1. Projects/Namespaces : Namespaces are a way to organize clusters into virtual sub-clusters — they can be helpful when different teams or projects share a Kubernetes cluster. Any number of namespaces are supported within a cluster, each logically separated from others but with the ability to communicate with each other. All namespaces and projects are listed here.

  1. Nodes : A Node is a worker machine in Kubernetes and may be either a virtual or a physical machine, depending on the cluster. Number of nodes present in the cluster. If you are using a single node cluster, there is only one entry.

If you are using multiple nodes then all are listed here :

You can get information about your Workload:

  1. DaemonSets : A DaemonSet ensures that all (or some) Nodes run a copy of a Pod. All the DaemonSets of the services are listed here.

  2. Deployments : Deployment provides declarative updates for Pods and ReplicaSets. All the deployments required for the 0chain setup are present here. (Like a miner, blobber, sharder, 0box, etc. )

  1. Pods : A pod is the smallest execution unit in Kubernetes. All pods are present here

Service Discovery

  1. Ingresses: Kubernetes Ingress is an API object that provides routing rules to manage access to the services within a Kubernetes cluster. All the Ingresses for Sharder, Miner, Explorer, etc. All the URLs are present here.

  1. Services : services connect a set of pods to an abstracted service name and IP address. Services provide discovery and routing between pods. All the services are listed here, Which we have launched.

Storage

  1. PersistentVolumes : A persistent volume is a piece of storage in a cluster that an administrator has provisioned.

  2. StorageClasses : Dynamic volume provisioning allows storage volumes to be created on-demand.

  3. ConfigMaps : A ConfigMap is an API object that allows you to store configuration for other objects to use.

  4. PersistentVolumesClaims : A persistent volume claim (PVC) is a request for storage, which is met by binding the PVC to a persistent volume (PV)

Last updated