chore: change emoji symbol on nuke task
This commit is contained in:
1 parent
d3806d3905
commit
cd8b55ec9a
1 file changed
+3
-3
@@ -200,7 +200,7 @@ In order to use Terraform and `cert-manager` with the Cloudflare DNS challenge y
|
||||
|
||||
📍 Here we will be running a Ansible Playbook to prepare Ubuntu for running a Kubernetes cluster.
|
||||
|
||||
📍 Nodes are not security hardened by default, you can do this with [dev-sec/ansible-collection-hardening](https://github.com/dev-sec/ansible-collection-hardening) or something similar.
|
||||
📍 Nodes are not security hardened by default, you can do this with [dev-sec/ansible-collection-hardening](https://github.com/dev-sec/ansible-collection-hardening) or similar if it supports Ubuntu 22.04.
|
||||
|
||||
1. Ensure you are able to SSH into your nodes from your workstation using your private ssh key. This is how Ansible is able to connect to your remote nodes. [How to configure SSH key-based authentication](https://www.digitalocean.com/community/tutorials/how-to-configure-ssh-key-based-authentication-on-a-linux-server)
|
||||
|
||||
@@ -218,7 +218,7 @@ In order to use Terraform and `cert-manager` with the Cloudflare DNS challenge y
|
||||
|
||||
📍 Here we will be running a Ansible Playbook to install [k3s](https://k3s.io/) with [this](https://galaxy.ansible.com/xanmanning/k3s) wonderful k3s Ansible galaxy role. After completion, Ansible will drop a `kubeconfig` in `./provision/kubeconfig` for use with interacting with your cluster with `kubectl`.
|
||||
|
||||
⚠️ If you run into problems, you can run `task ansible:nuke` to destroy the k3s cluster and start over.
|
||||
☢️ If you run into problems, you can run `task ansible:nuke` to destroy the k3s cluster and start over.
|
||||
|
||||
1. Verify Ansible can view your config by running `task ansible:list`
|
||||
|
||||
@@ -322,7 +322,7 @@ If Terraform was ran successfully you can log into Cloudflare and validate the D
|
||||
|
||||
🎉 **Congratulations** if all goes smooth you'll have a Kubernetes cluster managed by Flux, your Git repository is driving the state of your cluster.
|
||||
|
||||
⚠️ If you run into problems, you can run `task ansible:nuke` to destroy the k3s cluster and start over.
|
||||
☢️ If you run into problems, you can run `task ansible:nuke` to destroy the k3s cluster and start over.
|
||||
|
||||
🧠 Now it's time to pause and go get some coffee ☕ because next is describing how DNS is handled.
|
||||
|
||||
|
||||
Reference in new issue
Block a user