MetastoreService is the Schema for the MetastoreServices API. A managed metastore service that serves metadata queries.
Type
CRD
Group
dataproc.gcp.upbound.io
Version
v1beta1
apiVersion: dataproc.gcp.upbound.io/v1beta1
kind: MetastoreService
MetastoreServiceSpec defines the desired state of MetastoreService
No description provided.
Information used to configure the Dataproc Metastore service to encrypt customer data at rest. Structure is documented below.
Reference to a CryptoKey in kms to populate kmsKey.
Policies for referencing.
Selector for a CryptoKey in kms to populate kmsKey.
Policies for selection.
Configuration information specific to running Hive metastore software as the metastore service. Structure is documented below.
A mapping of Hive metastore version to the auxiliary version configuration. When specified, a secondary Hive metastore service is created along with the primary service. All auxiliary versions must be less than the service's primary version. The key is the auxiliary service name and it must match the regular expression a-z?. This means that the first character must be a lowercase letter, and all the following characters must be hyphens, lowercase letters, or digits, except the last character, which cannot be a hyphen. Structure is documented below.
Information used to configure the Hive metastore service as a service principal in a Kerberos realm. Structure is documented below.
A Kerberos keytab file that can be used to authenticate a service principal with a Kerberos Key Distribution Center (KDC). Structure is documented below.
The setting that defines how metastore metadata should be integrated with external services and systems. Structure is documented below.
The integration config for the Data Catalog service. Structure is documented below.
The configuration specifying the network settings for the Dataproc Metastore service. Structure is documented below.
The consumer-side network configuration for the Dataproc Metastore instance. Structure is documented below.
Reference to a Subnetwork in compute to populate subnetwork.
Policies for referencing.
Selector for a Subnetwork in compute to populate subnetwork.
Policies for selection.
Represents the scaling configuration of a metastore service. Structure is documented below.
The configuration specifying telemetry settings for the Dataproc Metastore service. If unspecified defaults to JSON. 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.
Information used to configure the Dataproc Metastore service to encrypt customer data at rest. Structure is documented below.
Reference to a CryptoKey in kms to populate kmsKey.
Policies for referencing.
Selector for a CryptoKey in kms to populate kmsKey.
Policies for selection.
Configuration information specific to running Hive metastore software as the metastore service. Structure is documented below.
A mapping of Hive metastore version to the auxiliary version configuration. When specified, a secondary Hive metastore service is created along with the primary service. All auxiliary versions must be less than the service's primary version. The key is the auxiliary service name and it must match the regular expression a-z?. This means that the first character must be a lowercase letter, and all the following characters must be hyphens, lowercase letters, or digits, except the last character, which cannot be a hyphen. Structure is documented below.
Information used to configure the Hive metastore service as a service principal in a Kerberos realm. Structure is documented below.
A Kerberos keytab file that can be used to authenticate a service principal with a Kerberos Key Distribution Center (KDC). Structure is documented below.
The setting that defines how metastore metadata should be integrated with external services and systems. Structure is documented below.
The integration config for the Data Catalog service. Structure is documented below.
The configuration specifying the network settings for the Dataproc Metastore service. Structure is documented below.
The consumer-side network configuration for the Dataproc Metastore instance. Structure is documented below.
Reference to a Subnetwork in compute to populate subnetwork.
Policies for referencing.
Selector for a Subnetwork in compute to populate subnetwork.
Policies for selection.
Represents the scaling configuration of a metastore service. Structure is documented below.
The configuration specifying telemetry settings for the Dataproc Metastore service. If unspecified defaults to JSON. 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.
MetastoreServiceStatus defines the observed state of MetastoreService.
No description provided.
Information used to configure the Dataproc Metastore service to encrypt customer data at rest. Structure is documented below.
Configuration information specific to running Hive metastore software as the metastore service. Structure is documented below.
A mapping of Hive metastore version to the auxiliary version configuration. When specified, a secondary Hive metastore service is created along with the primary service. All auxiliary versions must be less than the service's primary version. The key is the auxiliary service name and it must match the regular expression a-z?. This means that the first character must be a lowercase letter, and all the following characters must be hyphens, lowercase letters, or digits, except the last character, which cannot be a hyphen. Structure is documented below.
Information used to configure the Hive metastore service as a service principal in a Kerberos realm. Structure is documented below.
A Kerberos keytab file that can be used to authenticate a service principal with a Kerberos Key Distribution Center (KDC). Structure is documented below.
The setting that defines how metastore metadata should be integrated with external services and systems. Structure is documented below.
The integration config for the Data Catalog service. Structure is documented below.
The configuration specifying the network settings for the Dataproc Metastore service. Structure is documented below.
The consumer-side network configuration for the Dataproc Metastore instance. Structure is documented below.
Represents the scaling configuration of a metastore service. Structure is documented below.
The configuration specifying telemetry settings for the Dataproc Metastore service. If unspecified defaults to JSON. Structure is documented below.
Conditions of the resource.
default
apiVersion: dataproc.gcp.upbound.io/v1beta1
kind: MetastoreService
metadata:
annotations:
meta.upbound.io/example-id: dataproc/v1beta1/metastoreservice
labels:
testing.upbound.io/example-name: default
name: default
spec:
forProvider:
hiveMetastoreConfig:
- version: 2.3.6
location: us-central1
maintenanceWindow:
- dayOfWeek: SUNDAY
hourOfDay: 2
port: 9080
tier: DEVELOPER
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.