-
Notifications
You must be signed in to change notification settings - Fork 18
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
Charts will not deploy automatically #19
Comments
I think this happens because the Helm is looking for the You can manually set the required values to this:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This looks like a great solution but I've been struggling to get anything but the base piraeus-operator to deploy properly.
The first challenge was figuring out that the operator was not in the helm-charts repo. Easily fixed but it did take a few tries to realize it wasn't in the repo and that there wasn't another repo available. I just ended up creating my own helm repo for it.
I tried making the following as Chart dependencies for my application:
I also tried creating my own helm repo for the piraeus-operator and setting the above as Chart dependencies of the operator. In both cases, it will not deploy with the following error:
Please specify linstor.endpoint, no default URL could be determined
However, in the documentation it states that the linstor.endpoint does not need to be specified if it is deployed alongside and in the same namespace as the operator, which mine is.
I would set the linstor.endpoint if I knew what to set it to. It's not clear how I can determine the correct value.
Appreciate any insight into a typical approach to get this deployed using helm. I'd like to not resort to kubectl since it is less automated.
Thanks in advance...
The text was updated successfully, but these errors were encountered: