Skip to main content

Set Pod Size (CPU+RAM)

When you define your Deployment objects, you can specify the CPU and RAM requests for each container instance so you have the right size container/s for your application's needs.

Use the K8s Dashboard we provide or Kubectl to deploy or modify the Project Deployment for each Project.

note

You will not be able to specify specific locations or a minimum number of locations if they will cause your usage of RAM and CPU to exceed the boundaries of your current project plan.

Use the standard Kubernetes methods for specifying your container's requirements.

Example Configuration​

The following Deployment has one container defined with a request for 0.5 GiB RAM and 0.5 vCPU.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
  labels:
    app: nginx
spec:
  replicas: 1
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:1.14.2
        imagePullPolicy: Always
        resources:
          requests:
            memory: ".5Gi"
            cpu: "500m"
          limits:
            memory: ".5Gi"
            cpu: "500m"
        ports:
        - containerPort: 80

Refer to Kubernetes Docs on managing resources to learn more.

Additional Information​

  • There are no minimum sizes.
  • Maximum container sizes are 4 vCPU and 12 GiB.
  • For more information please contact us to understand how your requests are related to your billing.
  • CloudFlow may alter your YAML to ensure that request = limit, which gives a quality of service "Guaranteed".
    • Both request and limit must be specified
    • If request and limit are not equal, CloudFlow will use the higher of the two values.
  • You cannot request ephemeral storage directly. CloudFlow will automatically apply the ephemeral storage limits when the deployment is created.