Workspace

Proto: workspace.proto

Package: admin.gloo.solo.io

Types:

• WorkspaceReport
• WorkspaceReport.DestinationCountsEntry
• WorkspaceReport.ObjectReferences
• WorkspaceReport.PolicyCountsEntry
• WorkspaceReport.ResourcesEntry
• WorkspaceReport.SelectedCluster
• WorkspaceReport.SourceType
• WorkspaceSpec
• WorkspaceStatus
• WorkspaceStatus.DestinationCountsEntry
• WorkspaceStatus.NumResourcesEntry
• WorkspaceStatus.PolicyCountsEntry

WorkspaceReport link

WorkspaceReport.DestinationCountsEntry link

WorkspaceReport.ObjectReferences link

Represents a list of object references.

WorkspaceReport.PolicyCountsEntry link

WorkspaceReport.ResourcesEntry link

WorkspaceReport.SelectedCluster link

Represents a cluster that was successfully associated to a workspace based on the WorkspaceSpec.

WorkspaceReport.SourceType link

Represents whether a resource is imported, exported, or private to a workspace.

WorkspaceSpec link

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.

  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.

  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.

  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.

  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*
  

WorkspaceStatus link

WorkspaceStatus.DestinationCountsEntry link

WorkspaceStatus.NumResourcesEntry link

WorkspaceStatus.PolicyCountsEntry link