Home>

...

>

The Mismatch Scenario

The Mismatch Scenario

In this lesson, first, we will figure out what happens when a Namespace's defined limits are violated and then we will try creating and running Pods directly

Let’s see what happens when resources are defined, but they do not match the Namespace min and max limits.

Looking into the Definition

We’ll use the same go-demo-2.yml we used before.

Shell
cat res/go-demo-2.yml

The output, limited to the relevant parts, is as follows.

Shell
...
apiVersion: apps/v1beta2
kind: Deployment
metadata:
  name: go-demo-2-db
spec:
  ...
  template:
    ...
    spec:
      containers:
      - name: db
        image: mongo:3.3
        resources:
          limits:
            memory: "100Mi"
            cpu: 0.1
          requests:
            memory: "50Mi"
            cpu: 0.01
...
apiVersion: apps/v1beta2
kind: Deployment
metadata:
  name: go-demo-2-api
spec:
  ...
  template:
    ...
    spec:
      containers:
      - name: api
        ...
        resources:
          limits:
            memory: "10Mi"
            cpu: 0.1
          requests:
            memory: "5Mi"
            cpu: 0.01
...

What matters is that the resources for both Deployments are defined.

Creating Resources

Let’s create the objects and retrieve the events. They will help us understand better what is happening.

Shell
kubectl --namespace test apply \
    -f res/go-demo-2.yml \
    --record
kubectl --namespace test get events -w

The ...

Access this course and 1600+ top-rated courses and projects.