diff --git a/multipass-kubeadm-cluster/deployment/deploy.yaml b/multipass-kubeadm-cluster/deployment/deploy.yaml new file mode 100644 index 0000000..4c4123f --- /dev/null +++ b/multipass-kubeadm-cluster/deployment/deploy.yaml @@ -0,0 +1,36 @@ +apiVersion: apps/v1 +kind: Deployment +metadata: + labels: + app: asyncapi + name: asyncapi-deployment + namespace: asyncapi +spec: + replicas: 2 + selector: + matchLabels: + app: asyncapi + template: + metadata: + labels: + app: asyncapi + spec: + containers: + - name: asyncapi + image: iitaks.azurecr.io/asyncapi:1.2 + ports: + - containerPort: 80 +--- +apiVersion: v1 +kind: Service +metadata: + name: asyncapi-service + namespace: asyncapi +spec: + selector: + app: asyncapi + type: NodePort + ports: + - protocol: TCP + port: 80 + targetPort: 80 diff --git a/multipass-kubeadm-cluster/set-up-cluster-instructions.md b/multipass-kubeadm-cluster/set-up-cluster-instructions.md index 5df3787..1e03471 100644 --- a/multipass-kubeadm-cluster/set-up-cluster-instructions.md +++ b/multipass-kubeadm-cluster/set-up-cluster-instructions.md @@ -152,6 +152,17 @@ When the instance is ready, shell into the instance with `multipass shell worker ```bash sudo kubeadm join --token : --discovery-token-ca-cert-hash sha256: ``` + +[Important] +To get the exact information for the join run +```bash +multipass shell +``` +When inside, run +```bash +sudo kubeadm token create --print-join-command +``` + The information/token was generated with the kubeadm init command. If you need to recover the information, shell into `multipass shell cp1` and run