Optional: Include workload clusters in the workspace by using a selector. The selector matches the selector values in the KubernetesCluster resource on the management cluster. Selector is a map of {key,value} pairs. A single {key,value} in the selector map is equivalent to an element of labelRequirements, whose key field is “key”, the operator is “In”, and the values array contains only “value”. The requirements are ANDed.
Select the namespaces in the cluster(s) to include in the workspace. If you do not select any namespaces, the workspace is empty and results in an error.
configEnabled
bool
Optional: Enable configuration from this workload cluster. (default: true unless explicitly enabled for any selected clusters or namespaces)
ClusterSelector.NamespaceSelector
Select namespaces for the selected cluster(s)
Field
Type
Label
Description
name
string
name of the namespace to select. can use * to match name patterns in multiple namespaces.
configEnabled
bool
Optional: Enable configuration from this namespace. (default: true unless explicitly enabled for any selected clusters or namespaces)
ClusterSelector.SelectorEntry
Field
Type
Label
Description
key
string
value
string
WorkspaceSpec
Workspace describes a logical grouping of Kubernetes namespaces within the clusters that are part of a virtual mesh. Workspace can be treated as a boundary for configuration and service discovery. The specification describes how to select namespaces or/and clusters for a given workspace. The workspace-wide settings such as importFrom, exportTo are configured in the WorkspaceSettings object. Refer to the WorkspaceSettings documentation for details. The following example creates the web workspace that selects all workload clusters and all namespaces within those clusters to be part of the workspace. yaml apiVersion: admin.gloo.solo.io/v2 kind: Workspace metadata: name: web namespace: gloo-mesh spec: workloadClusters: - name: "*" namespaces: - name: "*" The following configuration creates the web workspace that selects the web namespace from all workload clusters that have the label of region: us-east to be part of the workspace. Refer to the KubernetesCluster documentation for examples on how to label your KubernetesCluster resource. yaml apiVersion: admin.gloo.solo.io/v2 kind: Workspace metadata: name: web namespace: gloo-mesh spec: workloadClusters: - selector: region: us-east namespaces: - name: web The following example creates the policy namespace that does NOT have any workload clusters. This workspace also has the gloo.solo.io/global label which other workspaces can use to import this workspace by label in their WorkspaceSettings resource. yaml apiVersion: admin.gloo.solo.io/v2 kind: Workspace metadata: name: policy namespace: gloo-mesh labels: gloo.solo.io/global: 'true' The example below creates the backend workspace that select any namespace that starts with ns1 in cluster1 and any namespace that starts with ns2 in cluster2. It has the gloo.solo.io/exportToGateway label, which other workspaces can use to import this workspace by label in their WorkspaceSettings resource. Refer to the KubernetesCluster documentation for examples on how to name your KubernetesCluster resource. yaml apiVersion: admin.gloo.solo.io/v2 kind: Workspace metadata: name: backend namespace: gloo-mesh labels: gloo.solo.io/exportToGateway: tier1 team: backend spec: workloadClusters: - name: cluster1 namespaces: - name: ns1* - name: cluster2 namespaces: - name: ns2*
Optional: Select workload clusters and namespaces for the workload clusters that are part of the workspace. When this is not specified, the workspace contains no workload clusters.
