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
Hi @abdennour, the NDB operator does not allocate storage on the Kubernetes cluster for the provisioned databases. Hence restricting the database size based on the namespace storage quota might not be functionally correct since the database storage is allocated on the Nutanix cluster.
cc: @krunal-jhaveri
Hi @manavrajvanshi , always storage is physically outside Kubernetes. But Think about kubernetes like a governance platform. As it can limit cpu & memory ( even this cpu &memory are Nutanix capacity ) , it can also limit storage. There should be away to bring the info of storage ( .status in not .spec ) & make it available for governance & reporting.
Is your feature request related to a problem? Please describe.
Yes! there is no limit of DB storage size can be managed/governed from kubernetes side.
Describe the solution you'd like
The operator should check the remaining quota & compare it with the requested storage (spec.databaseInstance.size).
Describe alternatives you've considered
As per now, We plan to use OPA with Gatekeeper to prevent exceeding the quota ( Redhat ACS,..etc)
Additional context
N/A
The text was updated successfully, but these errors were encountered: