kubectl describe(or another command) to output a spec? I don't see an option for it
get ... -o yaml
docker build. I’m guessing you need to use the ansible playbook there, but it could be great if the readme would be explicit about what are those steps. Thanks!
@almahmoud I checked the PVC using kubectl describe pvc and I got "FailedBinding 2m55s (x17605 over 3d1h) persistentvolume-controller no persistent volumes available for this claim and no storage class is set" (I am not sure if this is the correct way to check it).
Also I tried the tutorial which is in the link you sent, however I am getting "Error: rendered manifests contain a resource that already exists. Unable to continue with install: StorageClass "cvmfs-gxy-data" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "my-galaxy-release": current value is "cvmfs"; annotation validation error: key "meta.helm.sh/release-namespace" must equal "default": current value is "cvmfs""
Error after I try to execute "helm install my-galaxy-release cloudve/galaxy --set cvmfs.enabled=true --set cvmfs.deploy=true"
I tried to delete every pod, every namespace and every helm deployment to do a clean start, however, I still get this error.
cvmfsnamespace. This is only an issue because some resources, like the storage class, are not namespaced. So while the new release installed all the namespaced resources in
defaultnamespace for the new release, it conflicted with existing resources when trying to also create the cluster-wide resources such as the storage class. If it's not too hard, it might be worth just starting from a new cluster, adding the storage, and then trying again, rather than trying to clean up the existing one