FeaturestoreEntitytype is the Schema for the FeaturestoreEntitytypes API. An entity type is a type of object in a system that needs to be modeled and have stored information about.
Type
CRD
Group
vertexai.gcp.upbound.io
Version
v1beta1
apiVersion: vertexai.gcp.upbound.io/v1beta1
kind: FeaturestoreEntitytype
FeaturestoreEntitytypeSpec defines the desired state of FeaturestoreEntitytype
No description provided.
Reference to a Featurestore in vertexai to populate featurestore.
Policies for referencing.
Selector for a Featurestore in vertexai to populate featurestore.
Policies for selection.
The default monitoring configuration for all Features under this EntityType. If this is populated with [FeaturestoreMonitoringConfig.monitoring_interval] specified, snapshot analysis monitoring is enabled. Otherwise, snapshot analysis monitoring is disabled. Structure is documented below.
Threshold for categorical features of anomaly detection. This is shared by all types of Featurestore Monitoring for categorical features (i.e. Features with type (Feature.ValueType) BOOL or STRING). Structure is documented below.
The config for ImportFeatures Analysis Based Feature Monitoring. Structure is documented below.
Threshold for numerical features of anomaly detection. This is shared by all objectives of Featurestore Monitoring for numerical features (i.e. Features with type (Feature.ValueType) DOUBLE or INT64). Structure is documented below.
The config for Snapshot Analysis Based Feature Monitoring. 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.
Reference to a Featurestore in vertexai to populate featurestore.
Policies for referencing.
Selector for a Featurestore in vertexai to populate featurestore.
Policies for selection.
The default monitoring configuration for all Features under this EntityType. If this is populated with [FeaturestoreMonitoringConfig.monitoring_interval] specified, snapshot analysis monitoring is enabled. Otherwise, snapshot analysis monitoring is disabled. Structure is documented below.
Threshold for categorical features of anomaly detection. This is shared by all types of Featurestore Monitoring for categorical features (i.e. Features with type (Feature.ValueType) BOOL or STRING). Structure is documented below.
The config for ImportFeatures Analysis Based Feature Monitoring. Structure is documented below.
Threshold for numerical features of anomaly detection. This is shared by all objectives of Featurestore Monitoring for numerical features (i.e. Features with type (Feature.ValueType) DOUBLE or INT64). Structure is documented below.
The config for Snapshot Analysis Based Feature Monitoring. 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.
FeaturestoreEntitytypeStatus defines the observed state of FeaturestoreEntitytype.
No description provided.
The default monitoring configuration for all Features under this EntityType. If this is populated with [FeaturestoreMonitoringConfig.monitoring_interval] specified, snapshot analysis monitoring is enabled. Otherwise, snapshot analysis monitoring is disabled. Structure is documented below.
Threshold for categorical features of anomaly detection. This is shared by all types of Featurestore Monitoring for categorical features (i.e. Features with type (Feature.ValueType) BOOL or STRING). Structure is documented below.
The config for ImportFeatures Analysis Based Feature Monitoring. Structure is documented below.
Threshold for numerical features of anomaly detection. This is shared by all objectives of Featurestore Monitoring for numerical features (i.e. Features with type (Feature.ValueType) DOUBLE or INT64). Structure is documented below.
The config for Snapshot Analysis Based Feature Monitoring. Structure is documented below.
Conditions of the resource.
entity
apiVersion: vertexai.gcp.upbound.io/v1beta1
kind: FeaturestoreEntitytype
metadata:
annotations:
meta.upbound.io/example-id: vertexai/v1beta1/featurestoreentitytype
uptest.upbound.io/timeout: "3600"
labels:
testing.upbound.io/example-name: entity
name: entity
spec:
forProvider:
featurestoreSelector:
matchLabels:
testing.upbound.io/example-name: featurestore
labels:
foo: bar
monitoringConfig:
- categoricalThresholdConfig:
- value: 10
importFeaturesAnalysis:
- anomalyDetectionBaseline: PREVIOUS_IMPORT_FEATURES_STATS
state: ENABLED
numericalThresholdConfig:
- value: 0.8
snapshotAnalysis:
- disabled: false
monitoringIntervalDays: 1
stalenessDays: 21
name: terraform
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.