-
Bug
-
Resolution: Unresolved
-
Major
-
maistra-2.0.0
-
None
-
False
-
False
-
Undefined
-
There might be an issue when deploying a control plane into a project with resource quota. In this specific case; cpu, memory and limits.memory is required to deploy to this project.
SMCP.yaml:
...
runtime:
prometheus: #this will apply to prometheus
container:
resources:
limits:
memory: 256Mi
requests:
cpu: 25m
memory: 128Mi
defaults:
container:
#is be applied to prometheus-proxy and grafana-proxy
resources:
requests:
cpu: 101m
memory: 256Mi
limits:
cpu: 201m
memory: 512Mi
...
Prometheus deployment yaml:
...
- resources:
limits:
cpu: 201m
memory: 512Mi
requests:
cpu: 101m
memory: 256Mi
readinessProbe:
httpGet:
path: /oauth/healthz
port: https
scheme: HTTPS
timeoutSeconds: 1
periodSeconds: 10
successThreshold: 1
failureThreshold: 3
terminationMessagePath: /dev/termination-log
name: prometheus-proxy
...
- resources:
limits:
memory: 256Mi
requests:
cpu: 15m
memory: 128Mi
readinessProbe:
httpGet:
path: /-/ready
port: 9090
scheme: HTTP
timeoutSeconds: 1
periodSeconds: 10
successThreshold: 1
failureThreshold: 3
terminationMessagePath: /dev/termination-log
name: prometheus
...
- resources: {}
readinessProbe:
httpGet:
path: /healthz/ready
port: 15020
scheme: HTTP
initialDelaySeconds: 1
timeoutSeconds: 1
periodSeconds: 2
successThreshold: 1
failureThreshold: 30
terminationMessagePath: /dev/termination-log
name: istio-proxy
The istio-proxy in the prometheus pod does not get any resource parameters.
