From 48514e1e4ba18606f39f7f1cc2ef4b3de2ced096 Mon Sep 17 00:00:00 2001 From: Natanael Copa Date: Thu, 11 Apr 2024 16:12:00 +0200 Subject: [PATCH] Fix kubectl apply command in kubernetes quickstart This is similar to what is in vagrant quickstart docs. Signed-off-by: Natanael Copa --- docs/quickstarts/KUBERNETES.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/quickstarts/KUBERNETES.md b/docs/quickstarts/KUBERNETES.md index 9cc52acb..5b571b53 100644 --- a/docs/quickstarts/KUBERNETES.md +++ b/docs/quickstarts/KUBERNETES.md @@ -43,16 +43,16 @@ You will need to bring your own hardware (machine) for this guide. 1. Download and convert a cloud image to a raw image ```bash - kubectl apply -f https://raw.githubusercontent.com/tinkerbell/sandbox/main/vagrant/ubuntu-download.yaml + kubectl apply -n tink-system -f https://raw.githubusercontent.com/tinkerbell/sandbox/main/vagrant/ubuntu-download.yaml # This will download and convert the Ubuntu Jammy 22.04 cloud image. ``` 1. Create and/or customize Hardware, Template, and Workflow objects and apply them to the cluster. You can use the Hardware, Template, and Workflow in this repo, in the `vagrant/` directory, as a base from which to start. ```bash - kubectl apply -f my-hardware.yaml - kubectl apply -f my-template.yaml - kubectl apply -f my-workflow.yaml + kubectl apply -n tink-system -f my-hardware.yaml + kubectl apply -n tink-system -f my-template.yaml + kubectl apply -n tink-system -f my-workflow.yaml ``` 1. Start the machine provision process by rebooting, into a netbooting state, the machine you have specified in the Hardware object above.