I have a single yaml file in which I am attempting to deploy 2 load balancers, each with a single pod and container.

However, when I run the following infrastructure.yml file it starts 2 load balancers and only 1 pod / container (job-base). It is ignoring starting the api-base pod / container. Commenting out the job-base job / container from the file and the api-base pod starts properly.

What am I missing? How do I get this single file to deploy all pods, and services?

kind: ConfigMap
apiVersion: v1
metadata:
  name: api-base
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: api-base
spec:
  replicas: 1
  selector:
    matchLabels:
      app: api-base
  template:
    metadata:
      labels:
        app: api-base
    spec:
      containers:
      - name: api-base
        image: path/to/apiImage
        ports:
        - containerPort: 44360
          protocol: TCP
        resources:
          requests:
            memory: "0.4Gi"
            cpu: "0.2"
          limits:
            memory: "0.4Gi"
            cpu: "0.2"
---
apiVersion: v1
kind: Service
metadata:
   name: api-base
   labels:
      app: api-base
   annotations:
      service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
spec:
   selector:
      app: api-base
   ports:
    - port: 80
      targetPort: 44360
      protocol: TCP
   type: LoadBalancer
---
kind: ConfigMap
apiVersion: v1
metadata:
  name: job-base
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: job-base
spec:
  replicas: 1
  selector:
    matchLabels:
      app: job-base
  template:
    metadata:
      labels:
        app: job-base
    spec:
      containers:
      - name: job-base
        image: path/to/jobImage
        ports:
        - containerPort: 44360
          protocol: TCP
        resources:
          requests:
            memory: "0.4Gi"
            cpu: "0.2"
          limits:
            memory: "0.4Gi"
            cpu: "0.2"
---
apiVersion: v1
kind: Service
metadata:
   name: job-base
   labels:
      app: job-base
   annotations:
      service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
spec:
   selector:
      app: job-base
   ports:
    - port: 80
      targetPort: 44360
      protocol: TCP
   type: LoadBalancer

Update:

If it is not possible to accomplish this in a single yml I would also consider running the api and job containers in the same pod using the same load balancer. As long as I can expose each container within the pod on a different port.