Hi Wangda,
Which tool did you use to create the local K8s cluster?
If select the minikube, you should enable the ingress addon, execute
`minikube adons enable ingress` and get the right url by running `minikube
service submarine-traefik --url`. Then using the right url to access the
submarine in th
*Update:*
After restart K8s, the problem (cannot connect to notebook) is gone, I'm
not sure if there's anybody else hits the issue, it will be better if we
can add documentation to the user doc and help users to do troubleshooting.
Verified the following:
- Run example code inside the nodebook,
Nevermind, please ignore the previous message. I think it is caused by
previous installation (0.4.0), I reset K8s cluster and now everything can
be installed, trying to follow other steps now.
1) Why by default Submarine sever login has maria_dev as default user name?
2) There's no doc about usin
Hi Kevin,
Thank you so much for running this release.
Trying to follow the helm install stage, but notebook controller is failed
to start.
I downloaded RC1 source code, and follow the guidance:
https://github.com/apache/submarine/blob/master/docs/userdocs/k8s/helm.md
The pods in my system:
NAM
+1 for this RC1. Thanks Kevin drive this release and everyone for the great
works.
I've done the following tests:
1. Install the helm charts against the minikube
2. Install the helm charts against the kind
3. Check the UI's features, create the notebook/experiment and run work
BR,
Wanqiang Ji
On
-- Forwarded message -
寄件者： Xun Liu
Date: 2020年10月30日 週五 上午8:52
Subject: Re: [VOTE] Submarine-0.5.0-RC1 is ready for a vote!
To: Kevin Su
+1，
Version Submarine-0.5.0-RC1 has a great improvement in functionality, which
is great!
On Fri, Oct 30, 2020 at 8:48 AM Kevin Su wrote
Thanks for the great efforts! Kevin!
I've done the below testing
1. Verify the signatures (I signed Kevin's key and updated the KEYS file)
2. Build from source
3. Install the helm charts against Docker desktop k8s (v1.14.8)
4. Check basic UI's experiment and notebook features
And I like the built-
Curious -- I see mini-0.5.0-RC1 and RC0 docker images, however, the
operator, server, database and jupyter-notebook docker images are all
tagged version 0.5.0. Was this intentional?
I kept getting disk full error trying to pull the RC1 minisubmarine
image: docker pull apache/submarine:mini-0.5.0-R
Not a blocker, but I do notice our doc has lots of "TODO" and "FIXME" and
then realized our doc is a WIP from SUBMARINE-518.
I'd like to find a time to contribute to the docs later.
On Thu, Oct 22, 2020 at 4:16 AM Kevin Su wrote:
> Hi folks,
>
>
> Thanks to everyone's help on this release. Speci
Hi folks,
Thanks to everyone's help on this release. Special thanks to Wangda,
Zhankun, Xun, Wei-Chiu, Wanqiang, Ryan, Manikandan, and JohnTing!
I've created a release candidate (RC1) for submarine 0.5.0. The highlighted
features are as follows:
1. Submarine Experiments: Redefined the experim
10 matches
Mail list logo
