<div dir="ltr"><div dir="ltr"><div>Hi Christoph,</div><div><br></div><div>> You are using Pireaus operator to deploy LINSTOR, right?</div><div><br></div><div>No we're using <a href="https://github.com/kvaps/kube-linstor" target="_blank">https://github.com/kvaps/kube-linstor</a> and I'm going to add support of your stork plugin for that.</div><div><br></div><div><div>I'm little skeptical about using operator approach for anything else besides configuration or managing difficult application lifecycle :)<br></div><div>Instead, I like when application can be simple deployed by simple templated manifests. Kubernetes already have all needed controllers for managing it.</div><div><br></div><div>> I'll think about how to solve this more generically. Thanks for the report.</div><div><br></div><div>I'm sure that adding support for the same environment variables like for linstor-csi is the easiest and better way, ideally I'd like to have:</div><br></div><div> env:<br></div><div> - name: LINSTOR_IP<br> value: <a href="https://linstor-controller:3371" target="_blank">https://linstor-controller:3371</a><br> - name: LS_USER_CERTIFICATE<br> valueFrom:<br> secretKeyRef:<br> key: tls.crt<br> name: linstor-client-tls<br> - name: LS_USER_KEY<br> valueFrom:<br> secretKeyRef:<br> key: tls.key<br> name: linstor-client-tls<br> - name: LS_ROOT_CA<br> valueFrom:<br> secretKeyRef:<br> key: ca.crt<br> name: linstor-client-tls<br></div><div><br></div><div>And of course do not hardcode driver with the piraeus-operator. it's better to keep the things loosely coupled with each other, and components replaceable.</div><div><br></div><div>> the source code is available on GitHub, though it is somewhat hidden (in a
branch of our fork of Stork): <a href="https://github.com/LINBIT/stork/tree/linstor-driver" rel="noreferrer" target="_blank">https://github.com/LINBIT/stork/tree/linstor-driver</a><br>
</div><div><br></div><div>Got it! Sorry, this branch had no these changes at this weekend :)<br></div><div><br></div><div><div dir="ltr"><div dir="ltr"><div>Best Regards,</div><div>Andrei Kvapil<br></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 18, 2020 at 7:59 AM Christoph Böhmwalder <<a href="mailto:christoph.boehmwalder@linbit.com" target="_blank">christoph.boehmwalder@linbit.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 16.05.20 23:57, kvaps wrote:<br>
> Hi, I'm trying to deploy stork driver using official documentation. But it is<br>
> not starting due wrong controller endpoint name:<br>
> <br>
> time="2020-05-16T21:16:31Z" level=info msg="called: Init()"<br>
> time="2020-05-16T21:16:31Z" level=error msg="Error init'ing linstor driver:<br>
> error getting linstor endpoint: endpoints \"linstor-op-cs\" not found"<br>
> time="2020-05-16T21:16:31Z" level=info msg="Starting stork version 2.4.0-cba53f4c"<br>
> time="2020-05-16T21:16:31Z" level=info msg="Using driver linstor"<br>
> time="2020-05-16T21:16:31Z" level=fatal msg="Error getting Stork Driver linstor:<br>
> VolumeDriver with UID/Name: linstor not found"<br>
> <br>
> I can't find any configuration options, also I can't find any source code to<br>
> check it out.<br>
> <br>
> I've tried to assign similar variables like for csi-driver (LINSTOR_IP,<br>
> LS_USER_CERTIFICATE, LS_USER_KEY and LS_ROOT_CA), also try to create service<br>
> with `linstor-op-cs` name, but all my attempts to start the driver were even.<br>
> <br>
> - kvaps<br>
> <br>
> _______________________________________________<br>
> Star us on GITHUB: <a href="https://github.com/LINBIT" rel="noreferrer" target="_blank">https://github.com/LINBIT</a><br>
> drbd-user mailing list<br>
> <a href="mailto:drbd-user@lists.linbit.com" target="_blank">drbd-user@lists.linbit.com</a><br>
> <a href="https://lists.linbit.com/mailman/listinfo/drbd-user" rel="noreferrer" target="_blank">https://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
> <br>
<br>
Hi,<br>
<br>
You are using Pireaus operator to deploy LINSTOR, right?<br>
In that case hard coding "linstor-op-cs" was probably too naive (LINSTOR<br>
operator is our "enterprise support" version of Piraeus operator, so that is<br>
what we primarily test with).<br>
<br>
I'll think about how to solve this more generically. Thanks for the report.<br>
<br>
PS: the source code is available on GitHub, though it is somewhat hidden (in a<br>
branch of our fork of Stork): <a href="https://github.com/LINBIT/stork/tree/linstor-driver" rel="noreferrer" target="_blank">https://github.com/LINBIT/stork/tree/linstor-driver</a><br>
<br>
--<br>
Christoph Böhmwalder<br>
LINBIT | Keeping the Digital World Running<br>
DRBD HA — Disaster Recovery — Software defined Storage<br>
</blockquote></div>