Guideliness to run KVLite Container image in Kubernetes - development deployment only

[dario-vega]

Container image on GitHub repository

This GitHub repository contains Dockerfiles, documentation, and samples to build container images for Oracle NoSQL. In this GitHub discussion, I am providing guidelines to deploy this container image in Kubernetes.

This container image uses a simplified version of the Oracle NoSQL Database called KVLite. KVLite runs as a single process that provides a single storage node and single storage shard. KVLite does not include replication or administration.

Note: KVLite is NOT intended for production deployment or performance measurements.
We recommend testing with data that is NOT considered sensitive in nature. In other words, do not test with sensitive information such as usernames, passwords, credit card information, medication information, etc.

You can deploy this image in Kubernetes using the following YAML file. Just take care that the container image was configured to run under the user nosql-user. See the Dockerfile

We recommend assigning enough Memory Resources to Containers and Pods

apiVersion: v1
kind: Pod
metadata:
  name: oracle-nosql-kvlite
spec:
  securityContext:
    runAsUser: 1000
    fsGroup: 1000
  volumes:
  - name: kvroot-vol
    emptyDir: {}
  containers:
  - name: oracle-nosql-kvlite
    image: ghcr.io/oracle/nosql:latest-ce
    env:
    - name: KV_PROXY_PORT
      value: "8080"
    ports:
    - containerPort: 8080
      name: proxy-nosql
      protocol: TCP
    volumeMounts:
    - name: kvroot-vol
      mountPath: /kvroot
    securityContext:
      allowPrivilegeEscalation: false

You can configure your application containers to use the IP of the pod to contact Oracle NoSQL.

You can also run a single-instance stateful application in Kubernetes using a Deployment. The service allows other Pods in the cluster to access the database. The Service option clusterIP: None lets the Service DNS name resolve directly to the Pod's IP address.