Config sample for install in existent single node OpenShift cluster (SNO) using ODS as storage

IBM / cloud-pak-deployer

Configuration-based installation of OpenShift and Cloud Pak for Data/Integration/Watson AIOps on various private and public cloud infrastructure providers. Deployment attempts to achieve the end-state defined in the configuration. If something fails along the way, you only need to restart the process to continue the deployment.

https://ibm.github.io/cloud-pak-deployer/

Apache License 2.0

132 stars 67 forks source link

Config sample for install in existent single node OpenShift cluster (SNO) using ODS as storage #531

Open Pl0414141 opened 11 months ago

Pl0414141 commented 11 months ago

Is your feature request related to a problem? Please describe. Default installations of single node OpenShift via assisted cluster create LVM storages so default config do not work for work with this type of storage as is custom.

Describe the solution you'd like Use a config to deploy cloud pak to SNO cluster using LVM storage.

Describe alternatives you've considered Creating a LVM cluster storage via ODF LVM Operator and pass to the config the class name

fketelaars commented 11 months ago

Can you please state what kind of solution you are proposing?

LocalVolume storage --> this is not supported by most Cloud Paks
ODF storage --> Not sure if this a good match with single-node OpenShift

vincent-imt commented 11 months ago

ODF storage --> Not sure if this a good match with single-node OpenShift

I could use this feature too because when creating a single node OpenShift cluster in AWS I was not able to deploy with the components/services I needed because there is a ~ 26 volume EBS volume limit for a single EC2 instance. If there was ODF would this resolve the issue?