diff --git a/docs/getting-started/try-it-out/on-k3d-locally.mdx b/docs/getting-started/try-it-out/on-k3d-locally.mdx index 59034065..93b3b9b9 100644 --- a/docs/getting-started/try-it-out/on-k3d-locally.mdx +++ b/docs/getting-started/try-it-out/on-k3d-locally.mdx @@ -314,8 +314,8 @@ You can browse and modify the bootstrapped identity configuration (users, groups OpenChoreo needs some base resources before you can deploy anything: a project, environments, component types, and a deployment pipeline. These define what kinds of things you can build and where they run. - {`kubectl apply -f https://raw.githubusercontent.com/openchoreo/openchoreo/${versions.githubRef}/samples/getting-started/all.yaml && \\ -kubectl label namespace default openchoreo.dev/control-plane=true --overwrite`} + {`kubectl label namespace default openchoreo.dev/control-plane=true --overwrite && \\ +kubectl apply -f https://raw.githubusercontent.com/openchoreo/openchoreo/${versions.githubRef}/samples/getting-started/all.yaml`} **What was created:** diff --git a/docs/getting-started/try-it-out/on-your-environment.mdx b/docs/getting-started/try-it-out/on-your-environment.mdx index fa408345..64e0755f 100644 --- a/docs/getting-started/try-it-out/on-your-environment.mdx +++ b/docs/getting-started/try-it-out/on-your-environment.mdx @@ -466,16 +466,16 @@ curl -sk -o /dev/null -w "%{http_code}" https://console.${CP_BASE_DOMAIN}/ OpenChoreo needs some base resources before you can deploy anything: a project, environments, component types, and a deployment pipeline. - - {`kubectl apply -f https://raw.githubusercontent.com/openchoreo/openchoreo/${versions.githubRef}/samples/getting-started/all.yaml`} - - -Label the default namespace as a control plane namespace: +Label the default namespace as a control plane namespace first, then apply the resources: ```bash kubectl label namespace default openchoreo.dev/control-plane=true --overwrite ``` + + {`kubectl apply -f https://raw.githubusercontent.com/openchoreo/openchoreo/${versions.githubRef}/samples/getting-started/all.yaml`} + + ## Step 5: Setup Data Plane The data plane is where your workloads actually run. It has its own gateway for routing traffic, and a cluster-agent that connects back to the control plane to receive deployment instructions.