joel-bernstein opened a new issue #377:
URL: https://github.com/apache/solr-operator/issues/377
If you create a CR with the following resources:
` resources:
limits:
memory: 1Gi
requests:
cpu: 1000m
memory: 1Gi
`
Then get the json for the SolrCloud it will display:
` "resources": {
"limits": {
"memory": "1Gi"
},
"requests": {
"cpu": "1",
"memory": "1Gi"
}
},
`
What appears to be happening is that the solr-operator is reading the CR,
reformatting the cpu field and writing the CR back. I don't think this behavior
is correct. I believe the solr-operator should treat the CR as a read-only
object and not write back to it.
I could be wrong about how this transformation is occurring and I could be
wrong about the contract between the operator and the CR object being read
only. But I think it's worth a discussion about this as it effects how upstream
operators will interact with the solr operator.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
