-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Updated SageMaker operator Helm chart installation guide #1254
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
Updated SageMaker operator Helm chart installation guide #1254
Conversation
@cadedaniel to also review, please. |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
the \ ``values.yaml`` file, which includes high-level parameters for the | ||
Chart. Replace the ARN here with the ARN for the OIDC-based role you’ve | ||
the \ ``rolebased/values.yaml`` file, which includes high-level parameters for the | ||
Chart. Replace the role Arn here with the Arn for the OIDC-based role you’ve |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use ARN when referring to the Amazon Resource Name. For reference: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html#Conditions_ARN
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even within that document, the variable names refer to it as "Arn". I get confused as to when to use which capitalisation. I suppose it's "ARN" in documentation and "Arn" in code?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In documentation, we want to use Amazon Resource Name for the first usage, and ARN for subsequent usage. For code, the best practice is to conform to the standards being used.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
kubectl create namespace sagemaker-k8s-operator-system | ||
helm install --namespace sagemaker-k8s-operator-system sagemaker-operator rolebased/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should add a note that customers can pick their own namespace, but it must be specified in "system:serviceaccount:sagemaker-k8s-operator-system:sagemaker-k8s-operator-default"
in the trust.json
file. Otherwise, authentication won't work and customers will be confused.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great idea. Added a note directly underneath
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(optional) there are actually some fun directives you can use for formatting these kinds of things: https://sphinx-rtd-theme.readthedocs.io/en/stable/demo/demo.html#admonitions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a good way to check for syntax errors? (A make target?) I'd like to use the warning admonition
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, you can build the docs locally: https://github.com/aws/sagemaker-python-sdk#building-sphinx-docs
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
kubectl create namespace sagemaker-k8s-operator-system | ||
helm install --namespace sagemaker-k8s-operator-system sagemaker-operator rolebased/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(optional) there are actually some fun directives you can use for formatting these kinds of things: https://sphinx-rtd-theme.readthedocs.io/en/stable/demo/demo.html#admonitions
602985f
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Awesome. Ready to merge @laurenyu |
Issue #, if available:
Description of changes:
Updated the documentation for installation of the Amazon SageMaker Operator for Kubernetes helm charts.
Testing done:
Merge Checklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.General
Tests
unique_name_from_base
to create resource names in integ tests (if appropriate)By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.