Namespace Details

Namespace gke-managed-dpv2-observability

Workloads

Deployment hubble-relay

Containers

Container hubble-cli

Details

Guaranteed QoS

+$0/hour

Compare Current Config to Guaranteed QoS Recommendations
	Current		Guaranteed
CPU Request	500m	greater than	2m
CPU Limit	Not Set	error - not set	2m
Memory Request	2Gi	greater than	2Mi
Memory Limit	Not Set	error - not set	2Mi

YAML for Recommended Settings

resources:
  requests:
    cpu: 2m
    memory: 2Mi
  limits:
    cpu: 2m
    memory: 2Mi

Burstable QoS

+$0/hour

Compare Current Config to Burstable QoS Recommendations
	Current		Burstable
CPU Request	500m	greater than	1m
CPU Limit	Not Set	error - not set	2m
Memory Request	2Gi	greater than	1Mi
Memory Limit	Not Set	error - not set	2Mi

YAML for Recommended Settings

resources:
  requests:
    cpu: 1m
    memory: 1Mi
  limits:
    cpu: 2m
    memory: 2Mi

Container hubble-relay

Details

Guaranteed QoS

+$0/hour

Compare Current Config to Guaranteed QoS Recommendations
	Current		Guaranteed
CPU Request	500m	greater than	2m
CPU Limit	Not Set	error - not set	2m
Memory Request	2Gi	greater than	56Mi
Memory Limit	Not Set	error - not set	56Mi

YAML for Recommended Settings

resources:
  requests:
    cpu: 2m
    memory: 56Mi
  limits:
    cpu: 2m
    memory: 56Mi

Burstable QoS

+$0/hour

Compare Current Config to Burstable QoS Recommendations
	Current		Burstable
CPU Request	500m	greater than	1m
CPU Limit	Not Set	error - not set	2m
Memory Request	2Gi	greater than	25Mi
Memory Limit	Not Set	error - not set	57Mi

YAML for Recommended Settings

resources:
  requests:
    cpu: 1m
    memory: 25Mi
  limits:
    cpu: 2m
    memory: 57Mi

Container hubble-relay-metrics-collector

Details

Guaranteed QoS

+$0/hour

Compare Current Config to Guaranteed QoS Recommendations
	Current		Guaranteed
CPU Request	5m	greater than	2m
CPU Limit	Not Set	error - not set	2m
Memory Request	30Mi	greater than	22Mi
Memory Limit	30Mi	greater than	22Mi

YAML for Recommended Settings

resources:
  requests:
    cpu: 2m
    memory: 22Mi
  limits:
    cpu: 2m
    memory: 22Mi

Burstable QoS

+$0/hour

Compare Current Config to Burstable QoS Recommendations
	Current		Burstable
CPU Request	5m	greater than	1m
CPU Limit	Not Set	error - not set	2m
Memory Request	30Mi	greater than	21Mi
Memory Limit	30Mi	greater than	23Mi

YAML for Recommended Settings

resources:
  requests:
    cpu: 1m
    memory: 21Mi
  limits:
    cpu: 2m
    memory: 23Mi

Glossary

QoS: "QoS (Quality of Service) class is a designation assigned to a pod based on its resource requests and limits. Kubernetes uses QoS classes to make decisions about scheduling and evicting Pods." Kubernetes Documentation:
Configure Quality of Service for Pods
Guaranteed QoS: "For a Pod to be given a QoS class of Guaranteed:

Every Container, including init containers, in the Pod must have a memory limit and a memory request, and they must be the same.

Every Container, including init containers, in the Pod must have a CPU limit and a CPU request, and they must be the same."

Kubernetes Documentation:
Create a Pod That Gets Assigned a QoS Class of Guaranteed
Burstable QoS: "A Pod is given a QoS class of Burstable if:

The Pod does not meet the criteria for QoS class Guaranteed.

At least one Container in the Pod has a memory or CPU request."

Kubernetes Documentation:
Create a Pod That Gets Assigned a QoS Class of Burstable