You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: stack/README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
## Tinkerbell Stack Playground
2
2
3
-
The following section container the Tinkerbell stack playground instructions. It is not a production reference architecture.
4
-
Please use the [Helm chart](https://github.com/tinkerbell/charts) for production deployments.
3
+
The following section contains the Tinkerbell stack playground instructions. It is not a production reference architecture.
4
+
Please use the [Helm chart](https://github.com/tinkerbell/tinkerbell/tree/main/helm/tinkerbell) for production deployments.
5
5
6
6
## Quick-Starts
7
7
@@ -25,13 +25,13 @@ By default the Vagrant quickstart guides automatically install Ubuntu on the VM
25
25
vagrant ssh stack
26
26
```
27
27
28
-
1. Add your template. An example Template object can be found [here](https://github.com/tinkerbell/tink/tree/main/config/crd/examples/template.yaml) and more Template documentation can be found [here](https://tinkerbell.org/docs/concepts/templates/).
28
+
1. Add your template. Template documentation can be found [here](https://tinkerbell.org/docs/concepts/templates/).
29
29
30
30
```bash
31
31
kubectl apply -f my-OS-template.yaml
32
32
```
33
33
34
-
1. Create the workflow. An example Workflow object can be found [here](https://github.com/tinkerbell/tink/tree/main/config/crd/examples/workflow.yaml).
34
+
1. Create the workflow. Documentation on Workflows can be found [here](https://tinkerbell.org/docs/concepts/workflows/).
> These instructions above should be checked against the Charts repo before using. See the [README.md](https://github.com/tinkerbell/charts/tree/main/tinkerbell/stack) in the Helm chart repository for more information on how to use the Helm chart.
27
+
To install Tinkerbell, follow the official [install documentation](https://tinkerbell.org/docs/setup/install/).
35
28
36
29
1. Verify the stack is up and running
37
30
38
31
```bash
39
-
kubectl get pods -n tink-system# verify all pods are running
40
-
kubectl get svc -n tink-system# Verify the tink-stack service has the IP you specified with $LB_IP under the EXTERNAL-IP column
32
+
kubectl get pods -n tinkerbell# verify all pods are running
33
+
kubectl get svc -n tinkerbell# Verify the tink-stack service has the IP you specified with $LB_IP under the EXTERNAL-IP column
41
34
```
42
35
43
36
1. Download and convert a cloud image to a raw image
# This will download and convert the Ubuntu Jammy 22.04 cloud image.
48
41
```
49
42
50
-
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.
43
+
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 `stack/vagrant/` directory, as a base from which to start.
51
44
52
45
```bash
53
-
kubectl apply -n tink-system -f my-hardware.yaml
54
-
kubectl apply -n tink-system -f my-template.yaml
55
-
kubectl apply -n tink-system -f my-workflow.yaml
46
+
kubectl apply -n tinkerbell -f my-hardware.yaml
47
+
kubectl apply -n tinkerbell -f my-template.yaml
48
+
kubectl apply -n tinkerbell -f my-workflow.yaml
56
49
```
57
50
58
51
1. Start the machine provision process by rebooting, into a netbooting state, the machine you have specified in the Hardware object above.
59
52
60
53
1. Watch the progress of the workflow.
61
54
62
55
```bash
63
-
kubectl get workflow -n tink-system --watch
64
-
# Once the workflow is state is `STATE_SUCCESS`, you can login to the machine via the console or via SSH.
56
+
kubectl get workflow -n tinkerbell --watch
57
+
# Once the workflow state is `SUCCESS`, you can login to the machine via the console or via SSH.
0 commit comments