Navigation :
Get started
Concepts
Set up and manage Gloo Gateway
Configure gateway listeners
Process and route traffic
Control traffic with policies
Monitor health
Alpha: Portal
Gloo GraphQL module
Beta: AWS Lambda integration
Reference
-
API reference
-- AccessLogging
-- AccessLogPolicy
-- AccessPolicy
-- ActiveHealthCheckPolicy
-- ApiDoc
-- ApprovalState
-- AuthConfig
-- CaOptions
-- Clientmode
-- ClientTlsPolicy
-- CloudProvider
-- CloudProviderOptions
-- CloudResources
-- ConnectionPolicy
-- Core
-- CorsPolicy
-- CsrfPolicy
-- Cue
-- Dashboard
-- DlpPolicy
-- EnforcementLayers
-- ExtAuthPolicy
-- ExtAuthServer
-- ExternalEndpoint
-- ExternalService
-- ExternalWorkload
-- FailoverPolicy
-- FaultInjectionPolicy
-- GatewayLifecycleManager
-- GraphQLAllowedQueryPolicy
-- GraphQLPersistedQueryCachePolicy
-- GraphQLResolverMap
-- GraphQLSchema
-- GraphQLStitchedSchema
-- HeaderManipulation
-- HttpBufferPolicy
-- HttpMatchers
-- IstioLifecycleManager
-- IstioOperator
-- JwtPolicy
-- K8SReports
-- Keepalive
-- KubernetesCluster
-- ListenerConnectionPolicy
-- LoadBalancerPolicy
-- Locality
-- MirrorPolicy
-- OutlierDetectionPolicy
-- Phase
-- Port
-- Portal
-- PortalGroup
-- ProxyProtocolPolicy
-- Ratelimit
-- RatelimitClientConfig
-- RatelimitPolicy
-- RatelimitServerConfig
-- RatelimitServerSettings
-- Ref
-- References
-- RetryTimeoutPolicy
-- RootTrustPolicy
-- RouteTable
-- Selectors
-- SoloKit
-- Status
-- StringMatch
-- TcpMatchers
-- TlsMatchers
-- TransformationPolicy
-- TrimProxyConfigPolicy
-- VaultCa
-- VirtualDestination
-- VirtualGateway
-- WafPolicy
-- WasmDeploymentPolicy
-- WaypointLifecycleManager
-- Workspace
-- WorkspaceSettings
-
CLI reference
-
Helm value reference
-
Version reference
- Changelog
-
Security and CVE report
Troubleshoot issues
Get help and support
KubernetesCluster
Proto : kubernetes_cluster.proto
Package : admin.gloo.solo.io
Types :
KubernetesClusterReport
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.
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
Field
Description
clusterDomain
(string
) Optional: The cluster domain suffix this Cluster is configured with. Defaults to ‘cluster.local’.
KubernetesClusterStatus
Reflects the status of the Kubernetes cluster
Field
Description
common
(common.gloo.solo.io.Status
) Indicates the state of the Gloo agent that is connected to the Gloo management server.