k8 overview

Author: ranbel

src/content/docs/cloudflare-one/connections/connect-networks/deployment-guides/kubernetes.mdx

@@ -1,11 +1,35 @@
 ---
-pcx_content_type: how-to
+pcx_content_type: tutorial
 title: Kubernetes
 sidebar:
   order: 6
 ---
 
-[Kubernetes](https://kubernetes.io/) is a container orchestration and management tool. Kubernetes is declarative, so you define the end state in a .yml file. A Kubernetes cluster has two components, the master, and the workers. The master is the control plane that the user interacts with to manage the containers. Worker nodes are where the containers are deployed and run. A Kubernetes cluster is connected internally through a private network. Cloudflare Tunnel can be used to expose services running inside the Kubernetes cluster to the public.
+[Kubernetes](https://kubernetes.io/) is a container orchestration tool that helps deploy applications onto physical or virtual machines, scale the deployment, and push updates without downtime. The Kubernetes cluster, or environment, where the application instances are running is connected internally through a private network. You can install the `cloudflared` daemon inside of the Kubernetes cluster in order to connect the applications inside of the cluster to Cloudflare.
+
+![placeholder](~/assets/images/cloudflare-one/connections/connect-apps/handshake.jpg)
+
+As shown in the diagram, `cloudflared` runs as an adjacent deployment to the application deployments. `cloudflared` runs a Cloudflare Tunnel using a token and gains access to the Internet through the Kubernetes ingress controller. Once the cluster is connected to Cloudflare, you can add tunnel routes to control how `cloudflared` will proxy traffic to your Kubernetes services. For example, you could publish your Kubernetes application to the Internet or provide access only to internal WARP client users. Just like with other Kubernetes deployments, Kubernetes can spin up multiple replicas of `cloudflared` to ensure availability when incoming trafic changes. For more information about scaling Cloudflare Tunnel, refer to [Tunnel availability and failover](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-availability/).
+
+This tutorial will cover how to expose a Kubernetes service to the public Internet using `cloudflared`. For the purposes of this example, we will deploy a basic web application alongside `cloudflared` in Google Kubernetes Engine (GKE). The same principles apply to any other Kubernetes environment (such as `minikube` or `kubeadm`, or a cloud-based Kubernetes service) where `cloudflared` can connect to Cloudflare's network.
+
+## Create a tunnel
+
+Applications must be packaged into a containerized image, such as a Docker image, before you can run it in Kubernetes. Kubernetes uses the image to spin up multiple instances of the application.
+
+## Store the tunnel token
+
+## Set up the web app
+
+## Install and run the tunnel
+
+## Verify tunnel status
+
+## Add a tunnel route
+
+## Test the connection
+
+
 
 ## Creating the Kubernetes Cluster