Lab 1.3 - Deploy Hello-World Using ConfigMap w/ AS3

Just like the previous lab we’ll deploy the f5-hello-world docker container. But instead of using the Ingress resource we’ll use ConfigMap.

To deploy our application, we will need the following definitions:

  • Define the Deployment resource: this will launch our application running in a container.
  • Define the Service resource: this is an abstraction which defines a logical set of pods and a policy by which to access them. Expose the service on a port on each node of the cluster (the same port on each node). You’ll be able to contact the service on any <NodeIP>:NodePort address. When you set the type field to “NodePort”, the master will allocate a port from a flag-configured range (default: 30000-32767), and each Node will proxy that port (the same port number on every Node) for your Service.
  • Define the ConfigMap resource: this can be used to store fine-grained information like individual properties or coarse-grained information like entire config files or JSON blobs. It will contain the BIG-IP configuration we need to push.

Attention

The steps are generally the same as the previous lab, the big difference is the two resource types. Your Deployment and Service definitions are the same file.

App Deployment

On kube-master1 we will create all the required files:

  1. Create a file called deployment-hello-world.yaml

    Tip

    Use the file in ~/agilitydocs/docs/class1/kubernetes

    deployment-hello-world.yaml
     1
     2
     3
     4
     5
     6
     7
     8
     9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: f5-hello-world-web
      namespace: default
    spec:
      replicas: 2
      selector:
        matchLabels:
          app: f5-hello-world-web
      template:
        metadata:
          labels:
            app: f5-hello-world-web
        spec:
          containers:
          - env:
            - name: service_name
              value: f5-hello-world-web
            image: f5devcentral/f5-hello-world:latest
            imagePullPolicy: IfNotPresent
            name: f5-hello-world-web
            ports:
            - containerPort: 8080
              protocol: TCP
    
  2. Create a file called nodeport-service-hello-world.yaml

    Tip

    Use the file in ~/agilitydocs/docs/class1/kubernetes

    nodeport-service-hello-world.yaml
     1
     2
     3
     4
     5
     6
     7
     8
     9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    apiVersion: v1
    kind: Service
    metadata:
      name: f5-hello-world-web
      namespace: default
      labels:
        app: f5-hello-world-web
        cis.f5.com/as3-tenant: AS3
        cis.f5.com/as3-app: A1
        cis.f5.com/as3-pool: web_pool
    spec:
      ports:
      - name: f5-hello-world-web
        port: 8080
        protocol: TCP
        targetPort: 8080
      type: NodePort
      selector:
        app: f5-hello-world-web
    
  3. Create a file called configmap-hello-world.yaml

    Tip

    Use the file in ~/agilitydocs/docs/class1/kubernetes

    configmap-hello-world.yaml
     1
     2
     3
     4
     5
     6
     7
     8
     9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    apiVersion: v1
    kind: ConfigMap
    metadata:
      name: f5-as3-declaration
      namespace: default
      labels:
        f5type: virtual-server
        as3: "true"
    data:
      template: |
        {
            "class": "AS3",
            "declaration": {
                "class": "ADC",
                "schemaVersion": "3.10.0",
                "id": "urn:uuid:33045210-3ab8-4636-9b2a-c98d22ab915d",
                "label": "http",
                "remark": "A1 example",
                "AS3": {
                    "class": "Tenant",
                    "A1": {
                        "class": "Application",
                        "template": "http",
                        "serviceMain": {
                            "class": "Service_HTTP",
                            "virtualAddresses": [
                                "10.1.1.4"
                            ],
                            "pool": "web_pool",
                            "virtualPort": 80
                        },
                        "web_pool": {
                            "class": "Pool",
                            "monitors": [
                                "http"
                            ],
                            "members": [
                                {
                                    "servicePort": 8080,
                                    "serverAddresses": []
                                }
                            ]
                        }
                    }
                }
            }
        }
    
  4. We can now launch our application:

    kubectl create -f deployment-hello-world.yaml
    kubectl create -f nodeport-service-hello-world.yaml
    kubectl create -f configmap-hello-world.yaml
    
    ../../_images/f5-container-connector-launch-configmap-app.png
  5. To check the status of our deployment, you can run the following commands:

    Note

    This can take a few seconds to a minute to create these hello-world containers to running state.

    kubectl get pods -o wide
    
    ../../_images/f5-hello-world-pods2.png
    kubectl describe svc f5-hello-world
    
    ../../_images/f5-container-connector-check-app-definition-configmap.png

    Attention

    To understand and test the new app pay attention to the NodePort value, that’s the port used to give you access to the app from the outside. Here it’s “32734”, highlighted above.

  6. Now that we have deployed our application sucessfully, we can check the configuration on bigip1. Switch back to the open management session on firefox.

    Warning

    Don’t forget to select the proper partition. Previously we checked the “kubernetes” partition. In this case we need to look at the “AS3” partition. This partition was auto created by AS3 and named after the Tenant which happens to be “AS3”.

    Goto Local Traffic ‣ Virtual Servers

    Here you can see a new Virtual Server, “serviceMain” was created, listening on 10.1.1.4:80 in partition “AS3”.

    ../../_images/f5-container-connector-check-app-bigipconfig-as3.png
  7. Check the Pools to see a new pool and the associated pool members.

    GoTo: Local Traffic ‣ Pools and select the “web_pool” pool. Click the Members tab.

    ../../_images/f5-container-connector-check-app-pool-as3.png

    Note

    You can see that the pool members listed are all the cluster node IPs on port 32734. (NodePort mode)

  8. Access your web application via firefox on the jumpbox.

    Note

    Select the “Hello, World” shortcut or type http://10.1.1.4 in the URL field.

    ../../_images/f5-container-connector-access-app.png
  9. Hit Refresh many times and go back to your BIG-IP UI

    Goto: Local Traffic ‣ Pools ‣ Pool list ‣ “web_pool” ‣ Statistics to see that traffic is distributed as expected.

    ../../_images/f5-container-connector-check-app-bigip-stats-as3.png

    Note

    Why is all the traffic directed to one pool member? The answer can be found by instpecting the “serviceMain” virtual service in the management GUI.

  10. Scale the f5-hello-world app

    kubectl scale --replicas=10 deployment/f5-hello-world-web -n default
    
  11. Check that the pods were created

    kubectl get pods
    
    ../../_images/f5-hello-world-pods-scale10.png
  12. Check the pool was updated on bigip1. GoTo: Local Traffic ‣ Pools and select the “web_pool” pool. Click the Members tab.

    ../../_images/f5-hello-world-pool-scale10-as3.png

    Attention

    Why do we still only show 3 pool members?

  13. Remove Hello-World from BIG-IP.

    Attention

    In older versions of AS3 a “blank AS3 declaration” was required to completely remove the application/declaration from BIG-IP. In AS3 v2.20 and newer this is no longer a requirement.

    kubectl delete -f configmap-hello-world.yaml
    kubectl delete -f nodeport-service-hello-world.yaml
    kubectl delete -f deployment-hello-world.yaml
    

    Note

    Be sure to verify the virtual server and “AS3” partition were removed from BIG-IP. This can take up to 30s.

  14. Remove CIS:

    Important

    Verify the AS3 partition is removed before running the following command.

    kubectl delete -f nodeport-deployment.yaml
    

Important

Do not skip these clean-up steps. Instead of reusing these objects, the next lab we will re-deploy them to avoid conflicts and errors.