-
Bug
-
Resolution: Done
-
Normal
-
Logging 5.7.0
-
False
-
None
-
False
-
NEW
-
VERIFIED
-
-
-
Log Collection - Sprint 234
Description of problem:
The configurations of `kibana.proxy.resources` are not in kibana CR.
$ oc get cl instance -ojsonpath={.spec.visualization.kibana} |jq
{
"proxy": {
"resources": {
"requests": {
"cpu": "100m",
"memory": "200Mi"
}
}
},
"replicas": 1,
"resources": {
"requests": {
"cpu": "100m",
"memory": "1Gi"
}
}
}
$ oc get kibana kibana -ojsonpath={.spec} |jq
{
"managementState": "Managed",
"proxy": {
"resources": {}
},
"replicas": 1,
"resources": {
"requests": {
"cpu": "100m",
"memory": "1Gi"
}
}
}
Version-Release number of selected component (if applicable):
cluster-logging.v5.7.0
elasticsearch-operator.v5.7.0
How reproducible:
Always
Steps to Reproduce:
1. create clusterlogging with below file:
apiVersion: "logging.openshift.io/v1" kind: "ClusterLogging" metadata: name: "instance" namespace: openshift-logging spec: managementState: "Managed" logStore: elasticsearch: nodeCount: 3 redundancyPolicy: SingleRedundancy resources: requests: memory: 2Gi proxy: resources: requests: cpu: 150m memory: 300Mi storage: size: 20Gi storageClassName: standard-csi retentionPolicy: application: maxAge: 7h infra: maxAge: 3d audit: maxAge: 6h type: elasticsearch visualization: type: "kibana" kibana: resources: requests: cpu: 100m memory: 1Gi proxy: resources: requests: cpu: 100m memory: 200Mi replicas: 1 collection: type: "fluentd" resources: requests: cpu: 200m memory: 1Gi
2. check pods' resources
Actual results:
Configurations of `kibana.proxy.resources` in clusterlogging CR are not applied to kibana pod.
Expected results:
Kibana pod should be deployed with the settings in clusterlogging CR.
