diff --git a/app-dev/devops-and-containers/oke/oke-rm/README.md b/app-dev/devops-and-containers/oke/oke-rm/README.md index cf17e4226..293c8ad0c 100644 --- a/app-dev/devops-and-containers/oke/oke-rm/README.md +++ b/app-dev/devops-and-containers/oke/oke-rm/README.md @@ -56,7 +56,15 @@ By using this feature, we can modify the stack we deployed in Step 2 and add the ![Edit Terraform configurations](images/edit_oci_stack.png) -Instructions on how to modify the stack and add node pools can be found in the comments of the oke.tf file. +Instructions on how to modify the stack and add node pools can be found in comments on the bottom of the oke.tf file. Set create = true on the pool you want to be added by Terraform. + +Alternatively, clone this repo locally and edit oke.tf file to add a node pool and then load the folder including the modified Terraform to your RM stack: + +![Edit Terraform configurations](images/edit_stack_with_source.png) + +After adding the Terraform source save and apply the stack.Now, the RM should add the new pool: + +![Edit Terraform configurations](images/node_pool_create.png) ### Option 3.2: Create the OKE data plane with Ubuntu nodes @@ -78,4 +86,3 @@ Provisioning an OKE cluster is just the first step, be sure to also check out th * [OKE policies](../oke-policies/policies.md) * [GitOps with ArgoCD](../oke-gitops/README.md) * [Ingress guide](ingress.md) - diff --git a/app-dev/devops-and-containers/oke/oke-rm/images/edit_stack_with_source.png b/app-dev/devops-and-containers/oke/oke-rm/images/edit_stack_with_source.png new file mode 100644 index 000000000..3a74944b4 Binary files /dev/null and b/app-dev/devops-and-containers/oke/oke-rm/images/edit_stack_with_source.png differ diff --git a/app-dev/devops-and-containers/oke/oke-rm/images/node_pool_create.png b/app-dev/devops-and-containers/oke/oke-rm/images/node_pool_create.png new file mode 100644 index 000000000..d84415a9e Binary files /dev/null and b/app-dev/devops-and-containers/oke/oke-rm/images/node_pool_create.png differ