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

ODF Still deploys noobaa DB even when object storage is explicitly disabled #12

Open
mhjacks opened this issue Oct 15, 2024 · 0 comments

Comments

@mhjacks
Copy link

mhjacks commented Oct 15, 2024

For this specific set of values:

---
storageSystem:
  deploy: true
  inventory:
    useSpecificNodes: false

objectStorage:
  enable: false

The chart still deploys a noobaa database and some other things that might not be needed. For example:
(oc get all -n openshift-storage | grep noobaa)

pod/noobaa-core-0                                                     2/2     Running     0          24m
pod/noobaa-db-pg-0                                                    1/1     Running     0          24m
pod/noobaa-endpoint-66b85695b6-fcsxl                                  1/1     Running     0          23m
pod/noobaa-operator-64877484bf-dbm65                                  1/1     Running     0          31m
service/noobaa-db-pg                                             ClusterIP      172.30.197.14    <none>                                                                   5432/TCP                                                   24m
service/noobaa-mgmt                                              ClusterIP      172.30.141.206   <none>                                                                   80/TCP,443/TCP,8445/TCP,8446/TCP                           24m
service/noobaa-operator-service                                  ClusterIP      172.30.229.165   <none>                                                                   443/TCP                                                    31m
service/noobaa-syslog                                            ClusterIP      172.30.253.230   <none>                                                                   514/UDP                                                    24m
deployment.apps/noobaa-endpoint                                                1/1     1            1           23m
deployment.apps/noobaa-operator                                                1/1     1            1           31m
replicaset.apps/noobaa-endpoint-66b85695b6                                                1         1         1       23m
replicaset.apps/noobaa-operator-64877484bf                                                1         1         1       31m
statefulset.apps/noobaa-core    1/1     24m
statefulset.apps/noobaa-db-pg   1/1     24m
horizontalpodautoscaler.autoscaling/noobaa-hpav2   Deployment/noobaa-endpoint   0%/80%    1         2         1          23m
route.route.openshift.io/noobaa-mgmt   noobaa-mgmt-openshift-storage.apps.mhjacks-aeg.aws.validatedpatterns.io          noobaa-mgmt                                        mgmt-https   reencrypt/Redirect   None

I would think we would disable noobaa entirely, if possible. Maybe we can potentially use the {{- if .Values.objectStorage.enable -}} blolck to conditionalize more things?

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