Announcing the End of Support of the Original Version of SageMaker Operators for Kubernetes
This page announces the end of support for the original version of SageMaker Operators for
Kubernetes
End of Support Frequently Asked Questions
Contents
- Why are we ending support for the original version of SageMaker Operators for Kubernetes?
- Where can I find more information about the new SageMaker Operators for Kubernetes and ACK?
- What does end of support (EOS) mean?
- How can I migrate my workload to the new SageMaker Operators for Kubernetes for training and inference?
- Which version of ACK should I migrate to?
- Are the initial SageMaker Operators for Kubernetes and the new Operators (ACK service controller for Amazon SageMaker) functionally equivalent?
Why are we ending support for the original version of SageMaker Operators for Kubernetes?
Users can now take advantage of the ACK service controller
for Amazon SageMaker
For more information on ACK, see ACK
history and tenets
Where can I find more information about the new SageMaker Operators for Kubernetes and ACK?
-
For more information about the new SageMaker Operators for Kubernetes, see the ACK service controller for Amazon SageMaker
GitHub repository or read Amazon Controllers for Kubernetes Documentation . -
For a tutorial on how to train a machine learning model with the ACK service controller for Amazon SageMaker using Amazon EKS, see this SageMaker example
. For an autoscaling example, see Scale SageMaker Workloads with Application Auto Scaling
. -
For information on Amazon Controller for Kubernetes (ACK), see the Amazon Controllers for Kubernetes
(ACK) documentation. -
For a list of supported SageMaker resources, see ACK API Reference
.
What does end of support (EOS) mean?
While users can continue to use their current operators, we are no longer developing new
features for the operators, nor will we release any patches or security updates for any
issues found. v1.2.2
is the last release of SageMaker Operators
for Kubernetes
How can I migrate my workload to the new SageMaker Operators for Kubernetes for training and inference?
For information about migrating resources from the old to the new SageMaker Operators for Kubernetes, follow Migrate resources to the latest Operators.
Which version of ACK should I migrate to?
Users should migrate to the most recent
released version of the ACK service controller for Amazon SageMaker
Are the initial SageMaker Operators for Kubernetes and the new Operators (ACK service controller for Amazon SageMaker) functionally equivalent?
Yes, they are at feature parity.
A few highlights of the main notable differences between the two versions include:
-
The Custom Resources Definitions (CRD) used by the ACK-based SageMaker Operators for Kubernetes follow the Amazon API definition making it incompatible with the custom resources specifications from the SageMaker Operators for Kubernetes in its original version. Refer to the CRDs
in the new controller or use the migration guide to adopt the resources and use the new controller. -
The
Hosting Autoscaling
policy is no longer part of the new SageMaker Operators for Kubernetes and has been migrated to the Application autoscalingACK controller. To learn how to use the application autoscaling controller to configure autoscaling on SageMaker Endpoints, follow this autoscaling example . -
The
HostingDeployment
resource was used to create Models, Endpoint Configurations, and Endpoints in one CRD. The new SageMaker Operators for Kubernetes has a separate CRD for each of these resources.