Cluster is the Schema for the Clusters API. An Anthos cluster running on customer owned infrastructure.
Type
CRD
Group
containerattached.gcp.upbound.io
Version
v1beta1
apiVersion: containerattached.gcp.upbound.io/v1beta1
kind: Cluster
ClusterSpec defines the desired state of Cluster
No description provided.
Configuration related to the cluster RBAC settings. Structure is documented below.
Groups that can perform operations as a cluster admin. A managed ClusterRoleBinding will be created to grant the cluster-admin ClusterRole to the groups. Up to ten admin groups can be provided. For more info on RBAC, see https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles
Users that can perform operations as a cluster admin. A managed ClusterRoleBinding will be created to grant the cluster-admin ClusterRole to the users. Up to ten admin users can be provided. For more info on RBAC, see https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles
Binary Authorization configuration. Structure is documented below.
Logging configuration. Structure is documented below.
The configuration of the logging components Structure is documented below.
The components to be enabled. Each value may be one of: SYSTEM_COMPONENTS, WORKLOADS.
Monitoring configuration. Structure is documented below.
Enable Google Cloud Managed Service for Prometheus in the cluster. Structure is documented below.
OIDC discovery information of the target cluster. Kubernetes Service Account (KSA) tokens are JWT tokens signed by the cluster API server. This fields indicates how GCP services validate KSA tokens in order to allow system workloads (such as GKE Connect and telemetry agents) to authenticate back to GCP. Both clusters with public and private issuer URLs are supported. Clusters with public issuers only need to specify the issuer_url field while clusters with private issuers need to provide both issuer_url and jwks. Structure is documented below.
Support for proxy configuration. Structure is documented below.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
Configuration related to the cluster RBAC settings. Structure is documented below.
Groups that can perform operations as a cluster admin. A managed ClusterRoleBinding will be created to grant the cluster-admin ClusterRole to the groups. Up to ten admin groups can be provided. For more info on RBAC, see https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles
Users that can perform operations as a cluster admin. A managed ClusterRoleBinding will be created to grant the cluster-admin ClusterRole to the users. Up to ten admin users can be provided. For more info on RBAC, see https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles
Binary Authorization configuration. Structure is documented below.
Logging configuration. Structure is documented below.
The configuration of the logging components Structure is documented below.
The components to be enabled. Each value may be one of: SYSTEM_COMPONENTS, WORKLOADS.
Monitoring configuration. Structure is documented below.
Enable Google Cloud Managed Service for Prometheus in the cluster. Structure is documented below.
OIDC discovery information of the target cluster. Kubernetes Service Account (KSA) tokens are JWT tokens signed by the cluster API server. This fields indicates how GCP services validate KSA tokens in order to allow system workloads (such as GKE Connect and telemetry agents) to authenticate back to GCP. Both clusters with public and private issuer URLs are supported. Clusters with public issuers only need to specify the issuer_url field while clusters with private issuers need to provide both issuer_url and jwks. Structure is documented below.
Support for proxy configuration. Structure is documented below.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
ClusterStatus defines the observed state of Cluster.
No description provided.
Configuration related to the cluster RBAC settings. Structure is documented below.
Groups that can perform operations as a cluster admin. A managed ClusterRoleBinding will be created to grant the cluster-admin ClusterRole to the groups. Up to ten admin groups can be provided. For more info on RBAC, see https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles
Users that can perform operations as a cluster admin. A managed ClusterRoleBinding will be created to grant the cluster-admin ClusterRole to the users. Up to ten admin users can be provided. For more info on RBAC, see https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles
Binary Authorization configuration. Structure is documented below.
Fleet configuration. Structure is documented below.
Logging configuration. Structure is documented below.
The configuration of the logging components Structure is documented below.
The components to be enabled. Each value may be one of: SYSTEM_COMPONENTS, WORKLOADS.
Monitoring configuration. Structure is documented below.
Enable Google Cloud Managed Service for Prometheus in the cluster. Structure is documented below.
OIDC discovery information of the target cluster. Kubernetes Service Account (KSA) tokens are JWT tokens signed by the cluster API server. This fields indicates how GCP services validate KSA tokens in order to allow system workloads (such as GKE Connect and telemetry agents) to authenticate back to GCP. Both clusters with public and private issuer URLs are supported. Clusters with public issuers only need to specify the issuer_url field while clusters with private issuers need to provide both issuer_url and jwks. Structure is documented below.
Support for proxy configuration. Structure is documented below.
Workload Identity settings. Structure is documented below.
Conditions of the resource.
primary
apiVersion: containerattached.gcp.upbound.io/v1beta1
kind: Cluster
metadata:
annotations:
meta.upbound.io/example-id: containerattached/v1beta1/cluster
upjet.upbound.io/manual-intervention: This resource requires a valid issuerUrl value from the AKS or EKS cluster.
labels:
testing.upbound.io/example-name: primary
name: primary
spec:
forProvider:
description: Test cluster
distribution: aks
fleet:
- project: projects/${data.google_project.project.number}
location: us-west1
oidcConfig:
- issuerUrl: https://oidc.issuer.url
platformVersion: ${data.google_container_attached_versions.versions.valid_versions[0]}
project: ${data.google_project.project.project_id}
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.