Skip to content

Installing the Ambassador Gateway on k0s#

In this tutorial, you'll learn how to run k0s under Docker and configure it with the Ambassador API Gateway and a MetalLB service loadbalancer. We'll also deploy a sample service and expose it with an Ambassador mapping resource.

Utilizing the extensible bootstrapping functionality with Helm, it's as simple as adding the right extensions to the k0s.yaml file when configuring your cluster.

Running k0s under docker#

If you're not on a platform natively supported by k0s, running under docker is a viable option (see k0s in Docker). Since we're going to create a custom configuration file we'll need to map that into the k0s container - and of course we'll need to expose the ports required by Ambassador for outside access.

Start by running k0s under docker :

docker run -d --name k0s --hostname k0s --privileged -v /var/lib/k0s -p 6443:6443

Once running, export the default k0s configuration file using

docker exec k0s k0s default-config > k0s.yaml

and export the cluster config so you can access it with kubectl:

docker exec k0s cat /var/lib/k0s/pki/admin.conf > k0s-cluster.conf
export KUBECONFIG=$KUBECONFIG:<absolute path to k0s-cluster.conf>
(somewhat brute-force but gets the job done)

Configuring k0s.yaml#

Open the file in your favorite code editor and add the following extensions at the bottom:

      - name: datawire
      - name: bitnami
      - name: ambassador
        chartname: datawire/ambassador
        version: "6.5.13"
        namespace: ambassador
        values: |2
      - name: metallb
        chartname: bitnami/metallb
        version: "1.0.1"
        namespace: default
        values: |2
            - name: generic-cluster-pool
              protocol: layer2
(you might need to replace the IP with your local IP which you can find higher up in the generated file under spec.api.address)

As you can see it adds both Ambassador and Metallb (required for LoadBalancers) with corresponding repositories and (minimal) configurations. This example only uses your local network - providing a range of IPs for MetalLB that are addressable on your LAN is suggested if you want to access these services from anywhere on your network.

Now stop/remove your k0s container with docker stop k0s and docker rm k0s, then start it again with additional ports and the above config file mapped into it:

docker run --name k0s --hostname k0s --privileged -v /var/lib/k0s -v <path to k0s.yaml file>:/k0s.yaml -p 6443:6443 -p 80:80 -p 443:443 -p 8080:8080

Let it start, and eventually (this can take some time) you'll be able to list the Ambassador Services:

kubectl get services -n ambassador
NAME                          TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
ambassador-1611224811         LoadBalancer    80:30327/TCP,443:30355/TCP   2m11s
ambassador-1611224811-admin   ClusterIP    <none>        8877/TCP                     2m11s
ambassador-1611224811-redis   ClusterIP   <none>        6379/TCP                     2m11s

Install the Ambassador edgectl tool and run the login command:

edgectl login --namespace=ambassador localhost

This will open your browser and take you to the Ambassador Console - all ready to go.

Deploy / map a service#

Let's deploy and map the Swagger Petstore service; create a petstore.yaml file with the following content.

apiVersion: v1
kind: Service
  name: petstore
  namespace: ambassador
    - name: http
      port: 80
      targetPort: 8080
    app: petstore
apiVersion: apps/v1
kind: Deployment
  name: petstore
  namespace: ambassador
  replicas: 1
      app: petstore
    type: RollingUpdate
        app: petstore
        - name: petstore-backend
            - name: http
              containerPort: 8080
kind:  Mapping
  name: petstore
  namespace: ambassador
  prefix: /petstore/
  service: petstore

Once you've created this, apply it:

kubectl apply -f petstore.yaml
service/petstore created
deployment.apps/petstore created created

and you should be able to curl the service:

curl -k 'https://localhost/petstore/api/v3/pet/findByStatus?status=available'
[{"id":1,"category":{"id":2,"name":"Cats"},"name":"Cat 1","photoUrls":["url1","url2"],"tags":[{"id":1,"name":"tag1"},{"id":2,"name":"tag2"}],"status":"available"},{"id":2,"category":{"id":2,"name":"Cats"},"name":"Cat 2","photoUrls":["url1","url2"],"tags":[{"id":1,"name":"tag2"},{"id":2,"name":"tag3"}],"status":"available"},{"id":4,"category":{"id":1,"name":"Dogs"},"name":"Dog 1","photoUrls":["url1","url2"],"tags":[{"id":1,"name":"tag1"},{"id":2,"name":"tag2"}],"status":"available"},{"id":7,"category":{"id":4,"name":"Lions"},"name":"Lion 1","photoUrls":["url1","url2"],"tags":[{"id":1,"name":"tag1"},{"id":2,"name":"tag2"}],"status":"available"},{"id":8,"category":{"id":4,"name":"Lions"},"name":"Lion 2","photoUrls":["url1","url2"],"tags":[{"id":1,"name":"tag2"},{"id":2,"name":"tag3"}],"status":"available"},{"id":9,"category":{"id":4,"name":"Lions"},"name":"Lion 3","photoUrls":["url1","url2"],"tags":[{"id":1,"name":"tag3"},{"id":2,"name":"tag4"}],"status":"available"},{"id":10,"category":{"id":3,"name":"Rabbits"},"name":"Rabbit 1","photoUrls":["url1","url2"],"tags":[{"id":1,"name":"tag3"},{"id":2,"name":"tag4"}],"status":"available"}]

or you can open https://localhost/petstore/ in your browser and change the URL of the specification to https://localhost/petstore/api/v3/openapi.json (since we mapped it to the /petstore prefix).

If you navigate to the Mappings part of the Ambassador Console (opened above) you will see the corresponding PetStore mapping as configured.


This should get you all set with running Ambassador under k0s. If you're not running under Docker just skip the docker-related steps above - but make sure that you have updated the k0s configuration in the same way as above.

If you're stuck with or have any questions about Ambassador please try the Ambassador Slack to get help.