Skip to content

docs: label default namespace before applying base resources #625

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
LakshanSS merged 1 commit into from
May 15, 2026
Merged

docs: label default namespace before applying base resources #625

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions docs/getting-started/try-it-out/on-k3d-locally.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<CodeBlock language="bash">
{`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`}
</CodeBlock>

**What was created:**
Expand Down
10 changes: 5 additions & 5 deletions docs/getting-started/try-it-out/on-your-environment.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<CodeBlock language="bash">
{`kubectl apply -f https://raw.githubusercontent.com/openchoreo/openchoreo/${versions.githubRef}/samples/getting-started/all.yaml`}
</CodeBlock>

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
```

<CodeBlock language="bash">
{`kubectl apply -f https://raw.githubusercontent.com/openchoreo/openchoreo/${versions.githubRef}/samples/getting-started/all.yaml`}
</CodeBlock>

## 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.
Expand Down