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

Allow specifying nodeSelector for cloned database #2572

Open
dmildh-absci opened this issue Mar 11, 2024 · 0 comments
Open

Allow specifying nodeSelector for cloned database #2572

dmildh-absci opened this issue Mar 11, 2024 · 0 comments

Comments

@dmildh-absci
Copy link

Please, answer some short questions which should help us to understand your problem / question better?

  • Currently using registry.opensource.zalan.do/acid/postgres-operator:v1.10.1
  • Kubernetes
  • Running in Pord
  • Bug report

When trying to create a clone database from s3 specifying nodeSelectors I get the following error:

Error from server (BadRequest): error when creating "db-clone-test.yaml": postgresql in version "v1" cannot be handled as a postgresql: strict decoding error: unknown field "spec.nodeSelect

My yaml is pretty basic and looks like

apiVersion: "acid.zalan.do/v1"
kind: postgresql
metadata:
  name: db-clone
  namespace: test
spec:
  clone:
    uid: "0a4ascaf-159e-4cac-8ee3-5292fe46f5"
    cluster: "source-db"
    timestamp: "2024-03-12T00:00:33-08:00"
...
  nodeSelector:
    node-role.kubernetes.io/cluster-apps: ""
  tolerations:
    - key: node-role.kubernetes.io/cluster-apps
      operator: Equal
      effect: NoSchedule
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant