fix(cloudflared): update the docs. (#3602)

* fix(cloudflared): update the docs.

* Update charts/stable/cloudflared/docs/installation_notes.md

* Update charts/stable/cloudflared/docs/installation_notes.md

* Update charts/stable/cloudflared/docs/installation_notes.md

Co-authored-by: Stavros Kois <47820033+stavros-k@users.noreply.github.com>

charts/stable/cloudflared/Chart.yaml

@@ -1,7 +1,7 @@
 apiVersion: v2
 kubeVersion: ">=1.16.0-0"
 name: cloudflared
-version: 1.0.9
+version: 1.0.10
 appVersion: "2022.8.0"
 description: Client for Cloudflare Tunnel, a daemon that exposes private services through the Cloudflare edge.
 type: application

charts/stable/cloudflared/docs/installation_notes.md

@@ -1,16 +1,26 @@
 # Installation Notes
 
-- Go to [cloudflare team dash](https://dash.teams.cloudflare.com)
-  and create a tunnel or migrate a current tunnel(this action is not reversible)
+- Go to [cloudflare team dash](https://dash.teams.cloudflare.com) and create a tunnel or migrate a current tunnel (this action is not reversible) by going to access and then tunnels tab.
 
-- Copy the token from tunnel's overview **Install and run a connector** section.
+![cf-tunnel-access-tunnel.png](imgs/cf-tunnel-access.png)
 
-  This is what your token may look like.
+- Create a tunnel like so (or migrate a current one)
 
-  ```text
-  eyJhIjoiNDJhYmYwMTQzNGMyMeUzNDMzMTE1Y2M0YmFhZGY0YTciLCJ0IjoiNzBiNza5zTItMWViMS00MjdjaWFiZjEtZWMwdzIwNmQwZmI3IiwicyI6IlltRmxPV1ExTldZdE16a3lOUzAwsW1KbUxUZzJPVGN0Wm1VelptVmpaak00T1dZeiJ5
-  ```
+![cf-tunnel-tunnel-create.png](imgs/cf-tunnel-create.png)
 
-- Set `token` with **your** tunnel's token. the tunnel ID will NOT work.
-- Now you can manage the tunnel via cloudflare dash by setting a private network or create ingress rules for your services and domain, you can use this as a reverse proxy directly or use it in conjunction with traefik if you are behind a CGNAT, do not have a static IP, nor can not portforward 443(SSL).
-- Please note you MAY need to modify cloudflared Zero Trust various settings in order for this work out-of-the-box which is beyond the scope of this guide.
+- Copy **JUST** the token from tunnel's overview **Install and run a connector** section.
+
+![cf-tunnel-token.png](imgs/cf-tunnel-token.png)
+
+- Set the `token` with **your** tunnel's token. the tunnel ID will **NOT** work.
+- Now you can manage the tunnel via cloudflare dash by setting a private network or create ingress rules for your services and domain.
+
+![cf-tunnel-hostname](imgs/cf-tunnel-hostname.png)
+
+![cf-tunnel-priv-network](imgs/cf-tunnel-priv-network.png)
+
+Notes:
+
+- You MAY need to modify cloudflared Zero Trust various settings in order for this work out-of-the-box which is beyond the scope of this guide.
+
+- You can use this as a reverse proxy directly or use it in conjunction with traefik if you are behind a CGNAT, do not have a static IP, or can not port forward 443 (SSL).