Skip to content

Added migrate resources note to README #169

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Sep 9, 2022
Merged

Added migrate resources note to README #169

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4556097
Added migrate resources note to README
Sep 2, 2022
a885901
Added migrate resources section and link to adopt resources section
Sep 2, 2022
627b25f
Restructuring and small style edit
Sep 9, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 10 additions & 8 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,9 +63,11 @@ Head over to the [Manage Resources In Multiple AWS Accounts](https://aws-control

### 6.0 Adopt Resources

ACK controller provides to provide the ability to “adopt” resources that were not originally created by ACK service controller. Given the user configures the controller with permissions which has access to existing resource, the controller will be able to determine the current specification and status of the AWS resource and reconcile said resource as if the ACK controller had originally created it.
ACK controllers provide the ability to “adopt” resources that were not originally created by an ACK service controller. For more information, see [Adopting Existing AWS Resources](https://aws-controllers-k8s.github.io/community/docs/user-docs/adopted-resource/) in the ACK documentation.

Sample:
Example:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: the following sample demonstrates how to adopt a SageMaker Endpoint


Save the following sample to a file called `adopt-endpoint-sample.yaml`.
```yaml
apiVersion: services.k8s.aws/v1alpha1
kind: AdoptedResource
Expand All @@ -82,20 +84,18 @@ spec:
# target K8s CR name
name: xgboost-endpoint
```
Save the above to a file name adopt-endpoint-sample.yaml.

Submit the CR
Submit the CR:
```sh
kubectl apply -f adopt-endpoint-sample.yaml
```

Check for `ACK.Adopted` condition to be true under `status.conditions`

Check that the `ACK.Adopted` condition under `status.conditions` is `True`:
```sh
kubectl describe adoptedresource adopt-endpoint-sample
```

Output should look similar to this:
Your output should look similar to the following:
```yaml
---
kind: AdoptedResource
Expand Down Expand Up @@ -125,9 +125,11 @@ status:
type: ACK.Adopted
```

Check resource exists in cluster
Check that the resource exists in your cluster:
```sh
kubectl describe endpoints.sagemaker xgboost-endpoint
```

### 7.0 Migrate resources from the old SageMaker Operators for Kubernetes

For information about migrating resources from the old [SageMaker Operators for Kubernetes](https://github.com/aws/amazon-sagemaker-operator-for-k8s) to the ACK SageMaker controller, see [Migrate resources to the new SageMaker Operators for Kubernetes](https://docs.aws.amazon.com/sagemaker/latest/dg/kubernetes-sagemaker-operators-migrate.html) in the *Amazon SageMaker Developer Guide*.