I am trying it out and I am running into some issues outlined below.
I am using Minikube (version: v0.25.0) in my experiments.
1) I deployed the tiller-crd custom resource definition and then deployed the provided example. Eventually, the mariadb Pod deployment became Ready. My first question is once the Mariadb Pod becomes ready, how do I access it to verify that the database creds are working properly.
(Edit: I used kubectl port-forward to solve point 1).
2) In order to solve above problem, I thought of using the NodePort service type, which can be set in the original Mariadb chart. My thinking was that if I use NodePort, then I will be able to connect to the mariadb instance by using Minikube IP. So in order to set the NodePort service type,
I was wondering what should be the exact key to use in the values block in the mariadb.yaml? I tried 'service.type' and 'serviceType'. But both approaches did not work. In general, what is the protocol/convention for configuring values through the values block in the spec of a HelmRelease custom resource instance?
3) While trying step 2, I ended up creating several instances of HelmRelease objects. Now I am not able to delete them. kubectl delete helmreleases displays that the instances have been deleted, but when I do kubectl get helmreleases, the instances still show up.
4) In order to solve above, I thought let me delete the CRD and reinstall it. I did that. And to be doubly sure that there is no stray tiller instance, I first manually deleted tiller-deploy deployment from kube-system namepace. After reinstalling the CRD now I am getting following error on all the deployments:
kubectl apply -f mariadb5.yaml
Error from server (MethodNotAllowed): error when creating "mariadb5.yaml": the server does not allow this method on the requested resource (post helmreleases.helm.bitnami.com)
(Edit: 3, 4 are still an issue but I was able to go past them by deleting and recreating minikube vm).
Any help would be greatly appreciated in solving some of the above issues.
Hi,
This project seems interesting!
I am trying it out and I am running into some issues outlined below.
I am using Minikube (version: v0.25.0) in my experiments.
1) I deployed the tiller-crd custom resource definition and then deployed the provided example. Eventually, the mariadb Pod deployment became Ready. My first question is once the Mariadb Pod becomes ready, how do I access it to verify that the database creds are working properly.
(Edit: I used kubectl port-forward to solve point 1).
2) In order to solve above problem, I thought of using the NodePort service type, which can be set in the original Mariadb chart. My thinking was that if I use NodePort, then I will be able to connect to the mariadb instance by using Minikube IP. So in order to set the NodePort service type, I was wondering what should be the exact key to use in the values block in the mariadb.yaml? I tried 'service.type' and 'serviceType'. But both approaches did not work. In general, what is the protocol/convention for configuring values through the values block in the spec of a HelmRelease custom resource instance?
3) While trying step 2, I ended up creating several instances of HelmRelease objects. Now I am not able to delete them. kubectl delete helmreleases displays that the instances have been deleted, but when I do kubectl get helmreleases, the instances still show up.
4) In order to solve above, I thought let me delete the CRD and reinstall it. I did that. And to be doubly sure that there is no stray tiller instance, I first manually deleted tiller-deploy deployment from kube-system namepace. After reinstalling the CRD now I am getting following error on all the deployments:
kubectl apply -f mariadb5.yaml Error from server (MethodNotAllowed): error when creating "mariadb5.yaml": the server does not allow this method on the requested resource (post helmreleases.helm.bitnami.com)
(Edit: 3, 4 are still an issue but I was able to go past them by deleting and recreating minikube vm).
Any help would be greatly appreciated in solving some of the above issues.
Thanks!