Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
27 changes: 26 additions & 1 deletion docs/cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,32 @@ EOF
This triggers k0smotron controllers to setup the control plane in pods. Once k0smotron is done you can get the admin access kubeconfig:

```shell
kubectl get secret kmc-admin-kubeconfig-k0smotron-test -o jsonpath='{.data.value}' | base64 -d > ~/.kube/child.conf
kubectl get secret k0smotron-test-kubeconfig -o jsonpath='{.data.value}' | base64 -d > ~/.kube/child.conf
```

**Warning**: Depending on your configuration, the admin kubeconfig may not be pointing to the right address.
If the kubeconfig doesn't work by default, you'll need to set the right value in `<server URL>`.

```yaml
apiVersion: v1
clusters:
- cluster:
server: <server URL>
certificate-authority-data: <redacted>
name: k0s
contexts:
- context:
cluster: k0s
user: admin
name: k0s
current-context: k0s
kind: Config
preferences: {}
users:
- name: admin
user:
client-certificate-data: <redacted>
client-key-data: <redacted>
```

Once your control plane is ready you can start [adding worker nodes](join-nodes.md) into the newly created control plane.
2 changes: 1 addition & 1 deletion docs/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ metadata:
spec:
replicas: 1
k0sImage: k0sproject/k0s
K0sVersion: v1.27.1-k0s.0
k0sVersion: v1.27.1-k0s.0
service:
type: NodePort
apiPort: 30443
Expand Down