Endpoint is the Schema for the Endpoints API. Provides a SageMaker Endpoint resource.
Type
CRD
Group
sagemaker.aws.upbound.io
Version
v1beta1
apiVersion: sagemaker.aws.upbound.io/v1beta1
kind: Endpoint
EndpointSpec defines the desired state of Endpoint
No description provided.
The deployment configuration for an endpoint, which contains the desired deployment strategy and rollback configurations. See Deployment Config.
Automatic rollback configuration for handling endpoint deployment failures and recovery. See Auto Rollback Configuration.
Update policy for a blue/green deployment. If this update policy is specified, SageMaker creates a new fleet during the deployment while maintaining the old fleet. SageMaker flips traffic to the new fleet according to the specified traffic routing configuration. Only one update policy should be used in the deployment configuration. If no update policy is specified, SageMaker uses a blue/green deployment strategy with all at once traffic shifting by default. See Blue Green Update Config.
Defines the traffic routing strategy to shift traffic from the old fleet to the new fleet during an endpoint deployment. See Traffic Routing Configuration.
Specifies a rolling deployment strategy for updating a SageMaker endpoint. See Rolling Update Policy.
Batch size for rollback to the old endpoint fleet. Each rolling step to provision capacity and turn on traffic on the old endpoint fleet, and terminate capacity on the new endpoint fleet. If this field is absent, the default value will be set to 100% of total capacity which means to bring up the whole capacity of the old fleet at once during rollback. See Rollback Maximum Batch Size.
Reference to a EndpointConfiguration in sagemaker to populate endpointConfigName.
Policies for referencing.
Selector for a EndpointConfiguration in sagemaker to populate endpointConfigName.
Policies for selection.
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.
The deployment configuration for an endpoint, which contains the desired deployment strategy and rollback configurations. See Deployment Config.
Automatic rollback configuration for handling endpoint deployment failures and recovery. See Auto Rollback Configuration.
Update policy for a blue/green deployment. If this update policy is specified, SageMaker creates a new fleet during the deployment while maintaining the old fleet. SageMaker flips traffic to the new fleet according to the specified traffic routing configuration. Only one update policy should be used in the deployment configuration. If no update policy is specified, SageMaker uses a blue/green deployment strategy with all at once traffic shifting by default. See Blue Green Update Config.
Defines the traffic routing strategy to shift traffic from the old fleet to the new fleet during an endpoint deployment. See Traffic Routing Configuration.
Specifies a rolling deployment strategy for updating a SageMaker endpoint. See Rolling Update Policy.
Batch size for rollback to the old endpoint fleet. Each rolling step to provision capacity and turn on traffic on the old endpoint fleet, and terminate capacity on the new endpoint fleet. If this field is absent, the default value will be set to 100% of total capacity which means to bring up the whole capacity of the old fleet at once during rollback. See Rollback Maximum Batch Size.
Reference to a EndpointConfiguration in sagemaker to populate endpointConfigName.
Policies for referencing.
Selector for a EndpointConfiguration in sagemaker to populate endpointConfigName.
Policies for selection.
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.
EndpointStatus defines the observed state of Endpoint.
No description provided.
The deployment configuration for an endpoint, which contains the desired deployment strategy and rollback configurations. See Deployment Config.
Automatic rollback configuration for handling endpoint deployment failures and recovery. See Auto Rollback Configuration.
Update policy for a blue/green deployment. If this update policy is specified, SageMaker creates a new fleet during the deployment while maintaining the old fleet. SageMaker flips traffic to the new fleet according to the specified traffic routing configuration. Only one update policy should be used in the deployment configuration. If no update policy is specified, SageMaker uses a blue/green deployment strategy with all at once traffic shifting by default. See Blue Green Update Config.
Defines the traffic routing strategy to shift traffic from the old fleet to the new fleet during an endpoint deployment. See Traffic Routing Configuration.
Specifies a rolling deployment strategy for updating a SageMaker endpoint. See Rolling Update Policy.
Batch size for rollback to the old endpoint fleet. Each rolling step to provision capacity and turn on traffic on the old endpoint fleet, and terminate capacity on the new endpoint fleet. If this field is absent, the default value will be set to 100% of total capacity which means to bring up the whole capacity of the old fleet at once during rollback. See Rollback Maximum Batch Size.
Conditions of the resource.
e
apiVersion: sagemaker.aws.upbound.io/v1beta1
kind: Endpoint
metadata:
annotations:
meta.upbound.io/example-id: sagemaker/v1beta1/endpoint
upjet.upbound.io/manual-intervention: This resource is skipping because the
EndpointConfiguration resource on which this resource depends was skipped.
labels:
testing.upbound.io/example-name: e
name: e
spec:
forProvider:
endpointConfigNameSelector:
matchLabels:
testing.upbound.io/example-name: ec
region: us-east-1
tags:
Name: foo
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.