Proto: kubernetes_cluster.proto

Package: admin.gloo.solo.io

KubernetesClusterReport

The resources that the applied resource selects.

FieldDescription
state(common.gloo.solo.io.State)

KubernetesClusterSpec

KubernetesCluster defines a Kubernetes cluster that has been registered with Gloo Mesh for management. A KubernetesCluster must be created in order to connect the Gloo Mesh Agent with the Gloo Mesh Server. KubernetesCluster must be deployed to the management cluster in the gloo-mesh namespace. The name of the KubernetesCluster has to be unique among all managed workload clusters for a given Gloo Mesh management plane. The name or/and labels of a KubernetesCluster resource can be used in a Workspace resource to determine the workload clusters for a given workspace. Note: The KubernetesCluster resource name must be unique across the KubernetesCluster resources for other clusters that you register with Gloo. For simplicity, any KubernetesCluster resources that are created automatically for you during cluster registration use the same name as the workload cluster. However, the name of the KubernetesCluster resource is not required to match the name of the cluster.

The following example show a simple KubernetesCluster resource named cluster1 with cluster.local as its cluster domain:

  apiVersion: admin.gloo.solo.io/v2
kind: KubernetesCluster
metadata:
  name: cluster1
  namespace: gloo-mesh
spec:
  clusterDomain: cluster.local

The following example adds the region label to the KubernetesCluster resource:

  apiVersion: admin.gloo.solo.io/v2
kind: KubernetesCluster
metadata:
  name: cluster1
  namespace: gloo-mesh
  labels:
    region: us-east
spec:
  clusterDomain: cluster.local

The following example excludes the cluster from safe mode:

  apiVersion: admin.gloo.solo.io/v2
kind: KubernetesCluster
metadata:
  name: cluster1
  namespace: gloo-mesh
  labels:
    region: us-east
spec:
  clusterDomain: cluster.local
  skipWarming: true
FieldDescription
clusterDomain(string)

Optional: The cluster domain suffix this Cluster is configured with. Defaults to ‘cluster.local’.
skipWarming(bool)

Optional: Exclude this cluster from safe mode. If set to true: In the event that Redis and the Gloo management server restart and their cache and local memory are cleared, the Gloo management server does not wait for this cluster to send an input snapshot to start the translation. Note that clusters that never connected to the Gloo management server to sent at least one input snapshot are automatically excluded from safe mode.

KubernetesClusterStatus

The status of the KubernetesCluster after it is applied to your Gloo environment.

FieldDescription
common(common.gloo.solo.io.Status)

Indicates the state of the Gloo agent that is connected to the Gloo management server.
conditions(repeated common.gloo.solo.io.Condition)

List of conditions – observations of KubernetesCluster state