Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unsafe flags not respected #1866

Open
cars-matt-b opened this issue Nov 10, 2024 · 2 comments
Open

Unsafe flags not respected #1866

cars-matt-b opened this issue Nov 10, 2024 · 2 comments
Labels

Comments

@cars-matt-b
Copy link

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

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

  1. install 1.15.1 operator
  2. kubectl apply minimal cr

Versions

  1. Kubernetes 1.30
  2. Operator 1.15.1
  3. Database N/A

Anything else?

No response

@hors
Copy link
Collaborator

hors commented Nov 11, 2024

@cars-matt-b, please provide an example of your CR, and I will try to help you.

@hors
Copy link
Collaborator

hors commented Jan 13, 2025

@cars-matt-b any update?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants