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

Stackstorm-ha on Kubernetes with openstack Magnum #172

Closed
mpiscaer opened this issue Jan 25, 2021 · 2 comments
Closed

Stackstorm-ha on Kubernetes with openstack Magnum #172

mpiscaer opened this issue Jan 25, 2021 · 2 comments
Labels
question Further information is requested

Comments

@mpiscaer
Copy link

Hi,

I try to install Stackstorm-ha on Kubernetes what is running on Openstack Magnum.

When I run the command:
helm install -f stackstorm stackstorm/stackstorm-ha

This fails at creating persistent storages. When I created the storages manual before the deploy it all functional successful.

What is the best way to set the storageClassName to value csi-sc-cinderplugin ?

@arm4b arm4b added the question Further information is requested label Jan 25, 2021
@arm4b
Copy link
Member

arm4b commented Jan 25, 2021

I believe related issue was asked in the StackStorm HA in rancher PV/PVC/Storage Classes #168 .

This applies to K8s cluster configuration itself, rather then Helm chart.

Our recommendation is to configure the https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/ K8s cluster for Dynamic Volume Provisioning which is an automatic way to create the persistent volumes based on PersistentVolumeClaim storage requests coming from the specific Helm chart configurations (MongoDB and RabbitMQ in our case).

@cognifloyd
Copy link
Member

I think this is very similar to #18 which discusses alternative storage solutions for packs.
My PR in #199 creates a cluster-agnostic way for the chart to handle whatever storage is configured in the cluster. Since there are so many storage solutions out there, this chart really can't manage creating any Persistent Volumes or Persistent Volume Claims (or the other varied storage-related bits).
So, once you have your k8s cluster's storage solution configured, you can add the relevant volume definitions in values (once #199 is merged) to use your storage backend.

I'm closing this as I believe the issue is covered by other issues or PRs. Feel free to reopen if I misunderstood.

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

No branches or pull requests

3 participants