You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a POC using this operator so I wanted to get this working on a local Kind cluster (single node)
To do that, I needed to pull down the cluster size and proxy size. However, that requires explicit acknowledgement with the "unsafeFlags" property in the cluster spec.
Currently, trying to deploy the "minimal" cr provided leaves the cluster resource in error claiming that unsafeFlags must be set to true.
unsafeFlags is clearly added to the spec in the minimal cr provided, so I believe this to be a bug.
I have not tried any other version, so if this is a bug introduced with a certain version I wouldn't be able to help clue yall into which version initially saw this bug.
More about the problem
Namespace: percona
Labels: <none>
Annotations: <none>
API Version: pxc.percona.com/v1
Kind: PerconaXtraDBCluster
Metadata:
Creation Timestamp: 2024-11-10T23:07:51Z
Generation: 1
Resource Version: 34041
UID: a51d2d4f-9975-430b-a5ec-e757fb4ea0d0
Spec:
Cr Version: 1.15.1
Haproxy:
Enabled: true
Image: percona/haproxy:2.8.5
Size: 1
Logcollector:
Enabled: true
Image: percona/percona-xtradb-cluster-operator:1.15.1-logcollector-fluentbit3.1.4
Pxc:
Image: percona/percona-xtradb-cluster:8.0.36-28.1
Size: 1
Volume Spec:
Persistent Volume Claim:
Resources:
Requests:
Storage: 6G
Secrets Name: minimal-cluster-secrets
Tls:
Upgrade Options:
Apply: disabled
Schedule: 0 4 * * *
Status:
Backup:
Conditions:
Last Transition Time: 2024-11-10T23:07:51Z
Message: check safe defaults: PXC size must be at least 3. Set spec.unsafeFlags.pxcSize to true to disable this check
Reason: ErrorReconcile
Status: True
Type: error
Haproxy:
Logcollector:
Message:
Error: check safe defaults: PXC size must be at least 3. Set spec.unsafeFlags.pxcSize to true to disable this check
Pmm:
Proxysql:
Pxc:
Ready: 0
Size: 0
State: error
Events: <none>
Steps to reproduce
install 1.15.1 operator
kubectl apply minimal cr
Versions
Kubernetes 1.30
Operator 1.15.1
Database N/A
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Report
I'm working on a POC using this operator so I wanted to get this working on a local Kind cluster (single node)
To do that, I needed to pull down the cluster size and proxy size. However, that requires explicit acknowledgement with the "unsafeFlags" property in the cluster spec.
Currently, trying to deploy the "minimal" cr provided leaves the cluster resource in error claiming that unsafeFlags must be set to true.
unsafeFlags is clearly added to the spec in the minimal cr provided, so I believe this to be a bug.
I have not tried any other version, so if this is a bug introduced with a certain version I wouldn't be able to help clue yall into which version initially saw this bug.
More about the problem
Steps to reproduce
Versions
Anything else?
No response
The text was updated successfully, but these errors were encountered: