Installing kubernetes

Upgrading

local

Existing nsolid-kubernetes installs can be upgraded running the following command:

ctl apply -f conf/nsolid.quickstart.yml

Cloud

If deployed to a cloud (AWS, Azure, GCP, Bluemix) please make sure to make the necessary adjustments to conf/nsolid.cloud.yml

ctl apply -f conf/nsolid.cloud.yml

Quickstart

stall

Notes:

Access N|Solid Dashboard

• Default username: nsolid
• Default password: demo

tf "\nhttps://$(minikube ip):$(kubectl get svc nginx-secure-proxy --namespace=nsolid --output='jsonpath={.spec.ports[1].nodePort}')\n"

or

ctl get svc nginx-secure-proxy --namespace=nsolid

Uninstall N|Solid from Kubernetes cluster

ctl delete ns nsolid --cascade

Deploy Sample App with N|Solid

Quick Start

ample-app
er build -t sample-app:v1 .
ctl create -f sample-app.service.yml
ctl create -f sample-app.deployment.yml

NOTE: the container image in sample-app.deployment.yml must be set to match your docker image name. E.g. if you are using minikube and ran eval $(minikube docker-env), set the image to:

spec:
  containers:
    - name: sample-app
      image: sample-app:v1

Production Install

NOTE: Assumes kubectl is configured and pointed at your Kubernetes cluster properly.

ctl create -f conf/nsolid.namespace.yml

ssl req -x509 -nodes -newkey rsa:2048 -keyout conf/certs/nsolid-nginx.key -out conf/certs/nsolid-nginx.crt

/conf/nginx/htpasswd
sswd -cb ./conf/nginx/htpasswd {username} {password}

ctl create secret generic nginx-tls --from-file=conf/certs --namespace=nsolid

ctl create configmap nginx-config --from-file=conf/nginx --namespace=nsolid

ctl create -f conf/nsolid.services.yml

Make sure the zone matches the zone you brought up your cluster in!

ud compute disks create --size 10GB nsolid-console

We need to create our disks and then update the volumeIds in conf/nsolid.persistent.aws.yml.

Make sure the zone matches the zone you brought up your cluster in!

ec2 create-volume --availability-zone eu-west-1a --size 10 --volume-type gp2

There's no need to explicitly create a persistent disk, since the Azure Container Service provides a default StorageClass, which will dynamically create them as needed (e.g. when a Pod includes a PersistentVolumeClaim).

There's no need to explicitly create a persistent disk, since the Bluemix Container Service provides a default StorageClass, which will dynamically create them as needed (e.g. when a Pod includes a PersistentVolumeClaim).

ctl create -f conf/nsolid.persistent.gce.yml

ctl create -f conf/nsolid.persistent.aws.yml

There's no need to explicitly create a PersistentVolume object, since they will be dynamically provisioned by the default StorageClass.

There's no need to explicitly create a PersistentVolume object, since they will be dynamically provisioned by the default StorageClass.

ctl create -f conf/nsolid.cloud.yml

Debugging / Troubleshooting

Configuring Apps for N|Solid with Kubernetes

Make sure your docker image is build on top of nodesource/nsolid:carbon-latest.

 nodesource/nsolid:carbon-latest

When defining your application make sure the following ENV are set.

v:
- name: NSOLID_APPNAME
  value: sample-app
- name: NSOLID_COMMAND
  value: "console.nsolid:9001"
- name: NSOLID_DATA
  value: "console.nsolid:9002"
- name: NSOLID_BULK
  value: "console.nsolid:9003"

Optional flags:

v:
- name: NSOLID_TAGS
  value: "nsolid-carbon,staging"

A comma separate list of tags that can be used to filter processes in the N|Solid Console.

ctl get svc {service-name}

Accessing N|Solid Kubernetes objects

Make sure you use the --namespace=nsolid flag on all kubectl commands.

ctl config current-context // outputs current context
ctl config set-context {$context} --namespace=nsolid // make 'nsolid' the default namespace
ctl config set-context {$context} --namespace=default // revert to default

Running nsolid-cli

Verify CLI:

ctl exec {pod-name} -- nsolid-cli --remote=http://console.nsolid:6753 ping

minikube

Minikube is a bit different then a normal Kubernetes install. The DNS service isn't running so discovering is a bit more involved. IP addresses are not dynamically assigned, instead we must use the host ports the service is mapped to.

If your doing a lot of work with docker and minikube it is recommended that you run the following:

 $(minikube docker-env)

Service discovery

Get the kubernetes cluster ip address:

kube ip

To get the service port:

ctl get svc {$service-name} --output='jsonpath={.spec.ports[0].nodePort}'

Note: If your service exposes multiple ports you may want to examine with --output='json' instead.

Common Gotchas

If you get the following message when trying to run docker build or communicating with the Kubernetes API.

r response from daemon: client is newer than server (client API version: 1.24, server API version: 1.23)

Export the DOCKER_API_VERSION to match the server API version.

rt DOCKER_API_VERSION=1.23

License & Copyright