[
https://issues.apache.org/jira/browse/STREAMPIPES-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247101#comment-17247101
]
Patrick Wiener commented on STREAMPIPES-264:
--------------------------------------------
[~Kiryl Batsiukov] I experienced issues related to Docker Desktop's host mount
option. That's why I recommend using minikube as an alternative. I provided
updates of the helm chart for local testing in the current dev branch:
* [https://github.com/apache/incubator-streampipes-installer/tree/dev/k8s)]
When using minikube, you can then simply start a minikube instance by issuing:
{code:java}
minikube start --mount-string ${HOME}/streampipes-k8s:/streampipes-k8s --mount
--memory=4g --cpus=4
{code}
This would mount a new perstistent folder in your home directory that survives
deletion of the helm chart.
Can you try it?
> Cannot login after k8s restart
> ------------------------------
>
> Key: STREAMPIPES-264
> URL: https://issues.apache.org/jira/browse/STREAMPIPES-264
> Project: StreamPipes
> Issue Type: Bug
> Components: Installer
> Affects Versions: 0.67.0
> Environment: k8s
> Reporter: Kiryl Batsiukov
> Assignee: Patrick Wiener
> Priority: High
> Fix For: 0.68.0
>
>
> after installed from helm chart to k8s (on a Docker Desktop k8s instance),
> cannot login into the streampipes web UI after a cluster restart.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
