MySQL Bugs: #113118: update cpu limit in innodbclusters cr not work

Bug #113118	update cpu limit in innodbclusters cr not work
Submitted:	17 Nov 2023 8:29	Modified:	17 Nov 2023 23:24
Reporter:	Bing Ma (OCA)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Operator	Severity:	S2 (Serious)
Version:	mysql-operator-0.12.0	OS:	Ubuntu
Assigned to:		CPU Architecture:	Any

Description:
update cpu limit in innodbclusters cr not work, but the container's cpu limit not changed

===in ic resources
 containers:
    - image: release-ci.xxx.io/demo/community-server:8.2.0
      name: mysql
      resources:
        limits:
          cpu: "2"
          memory: 1Gi
        requests:
          cpu: 100m
          memory: 512Mi

===the container 

      resources:
        limits:
          cpu: '1'
          memory: 1Gi
        requests:
          cpu: 100m
          memory: 512Mi

How to repeat:
change the cpu limit in the ic cr

Thank you for your report.

Posted by developer:
 
Hi,
updating the limits is currently not allowed. However, specifying them at creation time is allowed. An example:

apiVersion: mysql.oracle.com/v2
kind: InnoDBCluster
metadata:
  name: mycluster
  namespace: mine
spec:
  instances: 3
  tlsUseSelfSigned: false
  router:
    instances: 1
    tlsSecretName: mycluster-router-tls-secret
  secretName: mycluster-cluster-secret
  imagePullPolicy : IfNotPresent
  baseServerId: 2000
  version: 8.3.0
  serviceAccountName: mycluster-sa
  tlsCASecretName: mycluster-ca-secret
  tlsSecretName: mycluster-tls-secret
  podSpec: 
    containers:
    - name: mysql
      resources:
        limits:
          cpu: 750m
          memory: 4096Mi
        requests:
          cpu: 250m
          memory: 2048Mi
    terminationGracePeriodSeconds: 10

Would be really great to be allowed to better comply with declarative aspect of kubernetes where what you declare is what is applied.