I am creating a Kubernetes Job, which needs a temporary database for processing its tasks. i am having 2 docker images. 1 which is the job and 1 which is a mysql database containing already the database and the data needed for the job

I want to do something like this:

apiVersion: batch/v1
kind: Job
metadata:
  name: afmigration
spec:
  backoffLimit: 3
  template:
    spec:
      restartPolicy: Never
      containers:
      - name: afmigration
        image: migrate-job:latest
        imagePullPolicy: Always
        ports:
        - containerPort: 8080
        env:
        - name: POSTGRES_USER
          valueFrom:
            secretKeyRef:
              name: postgres-credentials
              key: user

        - name: POSTGRES_PASSWORD
          valueFrom:
            secretKeyRef:
              name: postgres-credentials
              key: password

        - name: POSTGRES_HOST
          value: postgres-service
        - name: MYSQL_ROOT_PASSWORD
          value: root
        - name: MYSQL_DATABASE
          value: tmpdb
      - name: migration-test-data
        image: migration-test-data:latest
        imagePullPolicy: Always
        ports:
        - containerPort: 3306
        env:
        - name: MYSQL_ROOT_PASSWORD
          value: root
        - name: MYSQL_DATABASE
          value: tmpdb

The problem here is that the database is first not being started. Also I probably need to define a service to get access to the database from the job. But my biggest question is how can I then stop the database, when the job finishes?

Here is the dockerfile of the migration-test-data:

FROM mysql:8.0
COPY ./*.sql /docker-entrypoint-initdb.d/

Here is the dockerfile for the afmigration, which is the job:

FROM frolvlad/alpine-oraclejdk8:slim

ARG JAR_FILE

COPY target/${JAR_FILE} /app/afmigration.jar

WORKDIR /app

ENTRYPOINT ["java","-Djava.security.egd=file:/dev/./urandom","-jar","/app/afmigration.jar"]