Kubernetes keeps spawning Pods after deletion

You can populate a container's environment variables through the use of Secrets or ConfigMaps. Use Secrets when the data you are working with is sensitive (e.g. passwords), and ConfigMaps when it is not.

In your Pod definition specify that the container should pull values from a Secret:

apiVersion: v1
kind: Pod
metadata: 
  labels: 
    context: docker-k8s-lab
    name: mysql-pod
  name: mysql-pod
spec: 
  containers:
  - image: "mysql:latest"
    name: mysql
    ports: 
    - containerPort: 3306
    envFrom:
      - secretRef:
         name: mysql-secret

Note that this syntax is only available in Kubernetes 1.6 or later. On an earlier version of Kubernetes you will have to specify each value manually, e.g.:

env: 
- name: MYSQL_USER
  valueFrom:
    secretKeyRef:
      name: mysql-secret
      key: MYSQL_USER

(Note that env take an array as value)

And repeating for every value.

Whichever approach you use, you can now define two different Secrets, one for production and one for dev.

dev-secret.yaml:

apiVersion: v1
kind: Secret
metadata:
  name: mysql-secret
type: Opaque
data:
  MYSQL_USER: bXlzcWwK
  MYSQL_PASSWORD: bXlzcWwK
  MYSQL_DATABASE: c2FtcGxlCg==
  MYSQL_ROOT_PASSWORD: c3VwZXJzZWNyZXQK

prod-secret.yaml:

apiVersion: v1
kind: Secret
metadata:
  name: mysql-secret
type: Opaque
data:
  MYSQL_USER: am9obgo=
  MYSQL_PASSWORD: c2VjdXJlCg==
  MYSQL_DATABASE: cHJvZC1kYgo=
  MYSQL_ROOT_PASSWORD: cm9vdHkK

And deploy the correct secret to the correct Kubernetes cluster:

kubectl config use-context dev
kubectl create -f dev-secret.yaml

kubectl config use-context prod
kubectl create -f prod-secret.yaml

Now whenever a Pod starts it will populate its environment variables from the values specified in the Secret.

• Download the .jar from sourceforge, save it somewhere on your PC.
• Open eclipse.
• You need the "Package Explorer" window open - should be open by default I think, on the LHS.
• Right click, New -> Project, and select "Java Project"
• Click Next
• Give your project a name, can be basically anything, although there are naming standards. E.g MyProject
• Click Next, then click Finish.
• You'll now have a new project called MyProject in the Package Explorer window.
• Now you need to import the jar to your project:
• Create a folder in your project in which you'll keep any jars. Right click on "MyProject", New -> Folder and give it a name, say "x-jars"
• This folder will be created below MyProject. This is a real (system) folder, and you want to copy your jar into this folder. This folder will be located on your filesystem at ~eclipse-workspace/MyProject/x-jars/
• When copied into the x-jars folder, back in eclipse select MyProject and hit F5 to refresh. The jar will now show up under your x-jars folder (You can expand a folder contents by clicking the little triangles)
• Now you want to actually use your jar:
• Right click on "src" under MyProject (src is where you keep all your java classes). Do New -> Package, and per standard conventions give it a name like: com.mydomain.smpp and click Finish.
• Right Click on the resulting Package and do New -> Class, and give it a name, e.g MyTest, and click Finish.
• You'll now have the skeleton of a Java class in your main eclipse editor. This class lives in the Package com.mydomain.smpp. All classes should live in a package.
• Finally you need to make sure that the x-jars folder is included in your build (compile) path. Right click on MyProject, do Build Path -> Configure Build Path. On the Libraries tab click "Add JARS", and select the x-jars folder in MyProject.
• And that's it. I can't help you set up a trial SMPP app/class as there does not appear to be any docs or published API, but this is what you need to do to use the jar.