MockServer is available as a helm chart that allows you to run MockServer inside any Kubernetes environment.

Deploying MockServer Helm Chart

To run MockServer in Kubernetes the easiest way is to use the existing MockServer helm chart.

This is available by using as a chart repo, with the following command:

helm upgrade --install --namespace mockserver mockserver


If you have helm chart source folder (i.e. you have the repository cloned):

helm upgrade --install --namespace mockserver mockserver helm/mockserver

The two commands above will install MockServer into a namespace called mockserver with default configuration (as per the embedded values.yaml).

MockServer will then be available on domain name mockserver.mockserver.svc.cluster.local, as long as the namespace you are calling from isn't prevented (by network policy) to call the mockserver namespace.

To view the logs:

kubectl -n mockserver logs --tail=100 -l app=mockserver,release=mockserver

To wait until the deployment is complete run:

kubectl -n mockserver rollout status deployments mockserver

To check the status of the deployment without waiting, run the following command and confirm the mockserver has the Running status:

kubectl -n mockserver get po -l release=mockserver

Basic MockServer Configuration

Modify the arguments used to start the docker container by setting values explicitly using --set, as follows:

helm upgrade --install --namespace mockserver --set app.serverPort=1080 --set app.logLevel=INFO mockserver

The following values are supported:

  • app.serverPort (default: 1080)
  • app.logLevel (default: INFO)
  • app.proxyRemoteHost (no default)
  • app.proxyRemotePort (no default)
  • app.jvmOptions (no default)
  • image.snapshot (default: false) - set true to use latest snapshot version

For example configure a proxyRemoteHost and proxyRemotePort, as follows:

helm upgrade --install --namespace mockserver --set app.serverPort=1080 --set --set app.proxyRemotePort=443 mockserver

Double check the correct arguments have been passed to the pod, as follows:

kubectl -n mockserver logs -l app=mockserver,release=mockserver

Detailed MockServer Configuration

The MockServer helm chart also supports providing detailed configuration such as:

  • a properties file to configure all MockServer properties, or
  • a json expectation initialization file to initialize expectations at start-up.

This is done by deploying a configmap to kubernetes with files embedded in the yaml as shown in mockserver-config helm chart.

The MockServer helm chart to configure to control how to mount the files from the configmap, as follows:

  • app.mountConfigMap (default: false) - enables the mounting of the configmap into the MockServer container file system
  • app.mountedConfigMapName (default: mockserver-config) - name of the configmap (in the same namespace) to mount
  • app.propertiesFileName (default: - name of the property file in the configmap
  • app.initializationJsonFileName (default: initializerJson.json) - name of the JSON initialization file in the configmap
For example:
helm upgrade --install --namespace mockserver --set app.mountConfigMap=true --set app.mountedConfigMapName=mockserver-config --set --set app.initializationJsonFileName=initializerJson.json mockserver helm/mockserver

MockServer URL

Local Kubernetes Cluster (i.e. minikube, microk8s)

If the service type hasn't been modified the following will provide the MockServer URL from outside the cluster.

export NODE_PORT=$(kubectl get -n mockserver -o jsonpath="{.spec.ports[0].nodePort}" services mockserver)
export NODE_IP=$(kubectl get nodes -n mockserver -o jsonpath="{.items[0].status.addresses[0].address}")
echo http://$MOCKSERVER_HOST

To test the installation the following curl command should return the ports MockServer is bound to:

curl -v -X PUT http://$MOCKSERVER_HOST/status

Docker for Desktop

Docker for Desktop creates automatic port bindings for LoadBalancer or NodePort services.

In addition on MacOS Docker for Desktop runs inside Hyperkit so the node IP address is not reachable, therefore the only way to call NodePort or LoadBalancer services is via the port bindings added by Docker for Desktop.

If the service type hasn't been modified the following will provide the MockServer URL from outside the cluster.

export NODE_PORT=$(kubectl get -n mockserver -o jsonpath="{.spec.ports[0].nodePort}" services mockserver)
echo http://$MOCKSERVER_HOST

Outside Remote Kubernetes Cluster (i.e. Azure AKS, AWS EKS, etc)

kubectl -n mockserver port-forward svc/mockserver 1080:1080 &
echo http://$MOCKSERVER_HOST

Inside Kubernetes Cluster

If a DNS server has been installed in the Kubernetes cluster the following DNS name should be available mockserver.<namespace>.svc.cluster.local, i.e. mockserver.mockserver.svc.cluster.local

Helm Delete

To completely remove the chart:

helm delete mockserver --purge