-
Notifications
You must be signed in to change notification settings - Fork 268
Support tag updates in SageMaker resources #1732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
/cc @aws-controllers-k8s/sagemaker-maintainer |
This is a known limitation. Tags are only supported on create in sagemaker controller. Updating tags is not supported yet. afaik, same was the case with old operator. Is this a blocker? Also, updating model and endpoint config is not supported since this operation is not available on service side. We will find a place to document this. @a-hilaly thanks for tagging. Is the common tag handling mechanism implemented now? |
Thanks @surajkota. We are aware that model/ endpointconfig is immutable. |
Ack, Thank you |
Issues go stale after 90d of inactivity. |
/lifecycle frozen |
also interested in this :) |
Describe the bug
We recently migrated from old sagemaker operator to the new ACK controller.
When we tried to update the resource tags by editing the manifest, it is not reflected on SageMaker and
kubectl describe
shows below errorSteps to reproduce
kubectl apply -f model.yaml
Expected outcome
SageMaker CRs can be updated and reflected in aws console.
Environment
Prod, Staging
The text was updated successfully, but these errors were encountered: