Skip to main content

Kubernetes - Deploy speedtest in kubernetes

There's a very nice project for a self-hosted speedtest called 'librespeed' which can be used to host your own speedtest page. Since everything is moving to containers, it's a nice way to get familiar with Kubernetes and Docker (yml file at the end).

Requirements:
- A Kubernetes Cluster of any size or form
- Access to dockerhub

I'll be using the adolfintel/speedtest image for my deployment and have 2 replicas.

First, create a deployment
 [archy@kube01 ~]$ kubectl create deployment --image adolfintel/speedtest speedtest-kubernetes  
Change the replicas to 2

 [archy@kube01 ~]$ kubectl edit deployment speedtest-kubernetes  
 ...  
  replicas: 2  
 ...  
Next up, expose the deployment. I'm using a very basic Kubernetes setup, so there are no loadbalancers available. I'll be using the NodePort type to expose a port on all Kubernetes-Nodes.
 [archy@kube01 ~]$ kubectl expose deployment speedtest-kubernetes --name=speedtest-kubernetes --port=80 --type=NodePort  
Check the current services and check the random port
 [archy@kube01 ~]$ kubectl get service  
 NAME                  TYPE       CLUSTER-IP       EXTERNAL-IP    PORT(S)      AGE  
 kubernetes            ClusterIP  10.96.0.1        <none>         443/TCP      1h  
 speedtest-kubernetes  NodePort   10.107.110.250   <none>         80:32445/TCP 5s  
Currently, the port 32445 will be forwarded to the 'speedtest-kubernetes' service' Port 80, so your site should be available already but I don't want to have some random port assigned to it.
Specifying a port is possible by editing the service and changing the 'nodePort' value.
 [archy@kube01 ~]$ kubectl edit service speedtest-kubernetes  
 ...  
  - nodePort: 30080  
 ...  
Check the service again to see if everything has been overwritten
 [archy@kube01 ~]$ kubectl get service speedtest-kubernetes  
 NAME                  TYPE      CLUSTER-IP       EXTERNAL-IP    PORT(S)       AGE  
 speedtest-kubernetes  NodePort  10.107.110.250   <none>         80:30080/TCP  29s  
There's however a faster way of deploying this using a definition written in yaml.
Here's the commands from above in yaml:
 ---  
 apiVersion: apps/v1  
 kind: Deployment  
 metadata:  
   name: speedtest  
   labels:  
     app: speedtest  
   namespace: default  
 spec:  
   replicas: 2  
   selector:  
     matchLabels:  
       app: speedtest  
   strategy:  
     rollingUpdate:  
       maxSurge: 25%  
       maxUnavailable: 25%  
     type: RollingUpdate  
   template:  
     metadata:  
       labels:  
         app: speedtest  
     spec:  
       containers:  
         - name: speedtest  
           image: adolfintel/speedtest  
           imagePullPolicy: Always  
           resources:  
             requests:  
               cpu: "128m"  
               memory: "32Mi"  
             limits:  
               cpu: "512m"  
               memory: "128Mi"  
           terminationMessagePath: /dev/termination-log  
           terminationMessagePolicy: File  
       dnsPolicy: ClusterFirst  
       restartPolicy: Always  
       schedulerName: default-scheduler  
       securityContext: {}  
       terminationGracePeriodSeconds: 30  
 ---  
 apiVersion: v1  
 kind: Service  
 metadata:  
   labels:  
     app: speedtest  
   name: speedtest  
   namespace: default  
 spec:  
   externalTrafficPolicy: Cluster  
   ipFamilies:  
     - IPv4  
   ipFamilyPolicy: SingleStack  
   ports:  
     - nodePort: 30080  
       port: 80  
       protocol: TCP  
       targetPort: 80  
   selector:  
     app: speedtest  
   sessionAffinity: None  
   type: NodePort  
Applying this file will create the deployment and service all in one go:
 [archy@kube01 ~]$ kubectl apply -f speedtest.yml  
The port is now available using port 30080 on all Kubernetes Nodes.
Feel free to comment and / or suggest a topic

Comments

Popular posts from this blog

Dynamic DNS with BIND and ISC-DHCP

I personally prefer to work with hostnames instead of ip-addresses. If you have anything like freeipa or active directory, it will do that for you by registering the client you added to your realm to the managed dns and edit the records dynamically. We can achieve the same goal with just bind and isc-dhcp. I'll use a raspberry pi with raspbian 9 for this setup. So here is a quick tutorial on how to configure the isc-dhcp-server to dynamically update bind. First set a static ip to your server. [archy@ddns ~]$ sudo vim /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto eth0 iface eth0 inet static address 172.31.30.5 network 172.31.30.0 broadcast 172.31.30.255 netmask 255.255.255.0

LACP-Teaming on CentOS 7 / RHEL 7

What is teaming? Teaming or LACP (802.3ad) is a technique used to bond together multiple interfaces to achieve higher combined bandwith. NOTE: every clients speed can only be as high as the single link speed of one of the members. That means, if the interfaces I use in the bond have 1 Gigabit, every client will only have a maximum speed of 1 Gigabit. The advantage of teaming is, that it can handle multiple connections with 1 Gigabit. How many connections depends on the amount of your network cards. I'm using 2 network cards for this team on my server. That means I can handle 2 Gigabit connections at full rate on my server provided the rest of the hardware can deliver that speed. There also exists 'Bonding' in the Linux world. They both do the same in theory but  for a detailed comparison check out this  article about teaming in RHEL7 . To create a teaming-interface, we will first have to remove all the interface configurations we've done on the (soon to be) sla

Push logs and data into elasticsearch - Part 2 Mikrotik Logs

This is only about the setup of different logging, one being done with Filebeat and the other being done with sending logging to a dedicated port opened in Logstash using the TCP / UDP Inputs. Prerequesites: You'll need a working Elasticsearch Cluster with Logstash and Kibana. Start by getting the Log Data you want to structure parsed correctly. Mikrotik Logs are a bit difficult since they show you Data in the interface which is already enriched with Time / Date. That means a message that the remote logging will send to Logstash will look like this: firewall,info forward: in:lan out:wan, src-mac aa:bb:cc:dd:ee:ff, proto UDP, 172.31.100.154:57061->109.164.113.231:443, len 76 You can check them in the grok debugger and create your own filters and mapping. The following is my example which might not fit your needs. Here are some custom patterns I wrote for my pattern matching: MIKROTIK_DATE \b(?:jan(?:uary)?|feb(?:ruary)?|mar(?:ch)?|apr(?:il)?|may|jun(?:e)?|jul(?

FreeIPA - Integrating your DHCPD dynamic Updates into IPA

I recently went over my network configuration and noticed that the dhcp-leases were not pushed into the IPA-DNS yet. So I thought, why not do it now. The setup is very similar to setting it up on a single bind instance not managed by IPA (I've already written a guide about this here ). recently went over my network configuration and I noticed that I've never put my My setup is done with the following hosts: ipa01.archyslife.lan - 172.31.0.1 inf01.archyslife.lan - 172.31.0.5 First of all, create a rndc-key: [archy@ipa01 ~]$ sudo rndc-confgen -a -b 512 This will create the following file '/etc/rndc-key' [archy@ipa01 ~]$ sudo cat /etc/rndc.key key "rndc-key" { algorithm hmac-md5; secret "secret_key_here=="; }; We also need to make named aware of the rndc-key and allow our remote dhcp server to write dns entries: [archy@ipa01 ~]$ sudo vim /etc/named.conf ... include "/etc/rndc-key&quo

SSSD - Debugging PAM permission denied

Sometimes there's weird errors in IT that occur on random chance. I've had such an encounter with SSSD in combination with IPA(+AD-Trust) recently, where only sometimes, a connection to one of the IPA-Servers would fail with this error: Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: pam_sss(sshd:account): Access denied for user runner: 4 (System error) Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: fatal: Access denied for user runner by PAM account configuration [preauth] In my case, it was only happening sometimes when running a basic system setup role using ansible on every host in the entire environment. This way, there was no consistent pattern besides being the same host every time if it failed. First up, add the 'debug_level=X' to every section required in the /etc/sssd/sssd.conf where X is a number from 1 to 10 with 10 being the most verbose. Afterward, restart sssd and check the logs for any obvious problems. 1) If you are using local users, check the