on 09-Mar-2022 09:00
This article walks through my experience standing up a Customer Edge for F5 Distributed Cloud and running a basic workload with vk8s on Distributed Cloud App Stack. I used a very basic scenario so this is should be helpful to anyone looking to get some basic testing done. I also ran through part of this on my Live Stream show, At The Edge.
Some requirements for this build:
If you are performing this install as you are reading this article, then I would suggest kicking off a download of the Distributed Cloud image and then continue reading this article.
Here is some terminology that we need to define to start off with. I will define more as we progress.
First thing you will need to do is generate a "site token" from the Distributed Cloud Console. A site token authorizes a Edge node to join the Distributed Cloud Platform.
The most up to date steps can be followed here, under How To -> Site Management -> Create a VMware Site -> Deploy Site -> Create a Site Token.
Next, with everything downloaded, you will want to kick off the installation of the Distrbuted Cloud VM
This continues to be documented in the above linked document under the Install the Node on VMware ESXi Hypervisor section.
A couple things to note:
Next, continue onto the Register the VMware Site section of the documentation. You should see a Pending Registration from your Distributed Cloud node which you can accept into your tenant.
From there you should see your node .
You'll need to add a label to your node. This allows it to be identified and pulled into a Virtual Site later. Adding a label may not be entirely clear at first. Under the list of labels, you'll see it have a grey drop down box. You can just start typing in here. The label you can use is ves.io/siteName then I gave mine a value of blam-site.
Next, I'm creating a vk8s site. This is where I'll add the Virtual Site that was just created. The documentation for this is found here. Note that within a couple minutes, a cluster is up and running on my NUC!
With the vk8s instance up and running, we can now deploy a workload to it. We're going to deploy an NGINX container. Here is the documentation for this step however I'm going to note some specific things to what I built.
We'll be configuring the Workload Type as just Service.
When you get to Container Configuration, use the Private Registry we configured before and specify nginx as the image name.
You'll also be asked which Customer Virtual Site to Deploy. The list should have the one that we've already created.
There is also an option to specify Port to Advertise. This would be 80/TCP.
Now with a Workload deployed, I want to get it out onto the internet. The way to do that is through the creation of an HTTP Load Balancer object. I'm biased, but these are pretty cool. Maybe from working with BIG-IP for so long, I can appreciate a simplistic approach to things. You can do things like your rotating SSL certs from Let's Encrypt with a simple drop down option, as well as your HTTP->HTTPS redirect with a check box. Here's the documentation for it.
I will just note that I also went ahead and configured myself a subdomain from one of my domain names that I own. It's pretty straight forward to configure - at least the Distributed Cloud side of it. The configuration steps with your Domain Registrar may vary.
With that configured, I can specify a hostname as per below and the HTTP Load Balancer will take care of setting up it's own SSL/TLS certificate for it!
You'll be creating an Origin Pool as well. It's documented here but I'll also note for configuring the Origin Pool, in order to call upon the Workload we created, I selected:
Type of Origin Server: K8s Service name of Origin Server on given Sites
Optionally, you can add a health check. I created a basic one that simply does a GET /
Also note that if you chose not to configure deleted DNS, you'll need to go under Manage -> HTTP Load Balancers. You will see the new objects and they will list the CNAMES for these objects. With that, you can go to your DNS and create a record that points to the CNAME you retrieved.
Fantastic article and video. This is super helpful for anyone getting started with running k8s on CE.
Very Useful video, thank you Buulam for posting these steps and video.
Is there any other article states how to deploy cluster on CE? As far as I know, there are two modes: active/standby (VRRP) and all nodes are active (ECMP BGP), but I coulldn't find any articles going deep into the technical points.
@Mohamed_Salah_ no deep technical points, but there's setup details here: https://docs.cloud.f5.com/docs/how-to/site-management/create-vmw-site
You'll want to match the cluster names and then see the points under the "Multi-node site registrations" section