[Resource Quota Lecture] All objects must use either requests or limits

[abdennour]

What happens during that lecture is we configure the limits.cpu in the Resourcequote. But don't configure it in the tomcat-deployment instead we configure the Cpu requests.

Which occurs in the error we receive. If you change limits.cpu to requests.cpu everything works just fine.

Related Question(s)

• https://www.udemy.com/kubernetes-from-a-devops-kubernetes-guru/learn/v4/questions/5088982

[abdennour]

Here a possible solution:

apiVersion: v1
kind: ResourceQuota
metadata:
  name: compute-resources
spec:
  hard:
    limits.cpu: "400m"
---
apiVersion: apps/v1beta2
kind: Deployment
metadata:
  name: tomcat-deployment
spec:
  selector:
    matchLabels:
      app: tomcat
  replicas: 3
  template:
    metadata:
      labels:
        app: tomcat
    spec:
      containers:
      - name: tomcat
        image: tomcat:9.0
        ports:
        - containerPort: 8080
        resources:
          limits: # Instead of "requests:"
            cpu: "200m"

[jleetutorial]

@abdennour Thanks for the proposed solution, I have put up a PR, can you take a look? #21

[jleetutorial]

Actually shall we put both requests and limits in the tomcat-deployment?

[jleetutorial]

@abdennour

[abdennour]

@jleetutorial I think we should consider limits, requests or both.

The dependency follows those formulas:

𝔦∑limits_cpu(deployment[i]) <= limits_cpu(resource-quota) 
𝔦∑limits_memory(deployment[i]) <= limits_memory(resource-quota) 
𝔦∑requests_cpu(deployment[i]) <= requests_cpu(resource-quota) 
𝔦∑requests_memory(deployment[i]) <= requests_memory(resource-quota) 

Hence, I will merge your PR