Docker & Kubernetes: Enterprise Edition

Follow

Authentication

Countly Enterprise Edition Docker images are hosted in GCR (Google Container Registry). In order to get access to them, you'll need to set up service account authentication in your container engine. 

For plain Docker:

cat service-account.json | docker login -u _json_key --password-stdin https://gcr.io

For Kubernetes:

kubectl create secret docker-registry countly-registry \
  --docker-server=https://gcr.io \
  --docker-username=_json_key \
  --docker-password="$(cat service-account.json)"

Then:

imagePullSecrets:
  - name: countly-registry

 

Images

Countly has quite a few images for different environments and deployment scenarios:

Title Images Description
API/Frontend CentOS

gcr.io/countly-01/centos-api:latest

gcr.io/countly-01/centos-frontend:latest

Recommended. General CentOS-based split images.
API/Frontend Debian

gcr.io/countly-01/api:latest

gcr.io/countly-01/frontend:latest

 General Debian-based split images
Core

gcr.io/countly-01/countly-ee-core:latest

API & Frontend in one image. For simple low-load cases when you don't want to have overhead of multiple API & Frontend containers.

CentOS images are preferred currently since they're better optimised (smaller).

Core images are simpler to deploy (less containers), but allow less granular scalability as you have to carry all the frontend dependencies and RAM requirements along with every additional container you add. Countly API processes/containers account for ~99% of compute resources in high load cases.

 

Configuration

Please follow our configuration guide. Countly Enterprise Edition doesn't have any extra requirements for Docker-based installations. Standard setup would look like this:

env: 
- name: COUNTLY_PLUGINS
value: "mobile,web,desktop,some,more,plugins"
- name: COUNTLY_CONFIG__FILESTORAGE
value: "gridfs"
- name: COUNTLY_CONFIG__MONGODB
value: "mongodb://some.mongo.host/countly"
- name: COUNTLY_CONFIG_HOSTNAME
value: countly.example.com
- name: COUNTLY_CONFIG__MAIL_TRANSPORT
value: "nodemailer-smtp-transport"
- name: COUNTLY_CONFIG__MAIL_CONFIG_HOST
value: "smtp.example.com"
- name: COUNTLY_CONFIG__MAIL_CONFIG_PORT
value: 25
- name: COUNTLY_CONFIG__MAIL_CONFIG_AUTH_USER
value: "example-user"
- name: COUNTLY_CONFIG__MAIL_CONFIG_AUTH_PASS
value: "example-password"

Also please note that Countly Enterprise Edition uses more MongoDB databases than Community Edition, therefore you'll need to ensure that one of these is true (in the order of preference):

  • You have no authentication for MongoDB.
  • Authentication is made against admin database.
  • Authentication is the same across all the databases and they do exist.

Please follow Securing MongoDB guide for more details. 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.