Skip to content
JamfPro Kubernetes manifest examples
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.


Type Name Latest commit message Commit time
Failed to load latest commit information.

JamfPro Kubernetes Manifests

JamfPro Kubernetes manifest examples


A set of Kubernetes manifests for creating a clustered JamfPro instance. Includes the clustered Tomcat statefulset, a service, and an ingress. Also includes Memcached and MySQL statefulsets to get a test instance up and running quickly.


  • A Kubernetes cluster
  • Kubernetes storage classes for data persistence and log file persistence ( mysql-storage and log-storage )
  • JamfPro manual install ROOT.war, unzipped and made into a data container image ( see Dockerfile as example )
  • Ingress controller supporting cookie affinity annotations ( e.g. HAProxy )

Other Notes

The log and mysql storage classes included in this repo are setup for local minikube usage and should be able to be utilized when testing locally.

Within the Tomcat manifest, there is hardcoded mysql server up check before proceeding with starting the JamfPro instance. If using a different Kubernetes service or an external database persistence this will need to be modified/removed accordingly.

Also within the Tomcat manifest is a hardcoded MEMCACHED_HOST value. Remove the environment variable to disable Memcached or modify the hostname according to your own environment setup.

When upgrading a clustered JamfPro instance, the master node MUST be upgraded first to process any database migrations before upgrading the non-master node(s). This can be accomplished by changing the statefulset update strategy to OnDelete

-- OR --

Modify the MASTER_NODE_NAME to be the highest ordinal of the statefulset to allow a rolling update to function as expected.

We do not currently publicly publish JamfPro releases to be utilized as data images, you must download a manual ROOT.war from JamfNation to create the required data container image.

The Tomcat image found in the tomcat.yaml manifest may not be the most current, please follow releases in our other Github repo JamfPro to ensure your image is the most current.


If running a local minikube startup should be as simple as creating a data image container availabe to your minikube instance and running from within this directory:

kubectl create -f .

Data Image Creation Example

unzip ROOT.war
docker build -t jamfpro-build .
You can’t perform that action at this time.