Hi Xiang Chen, I've heard discussions about multi-tenancy before. The general idea is this. When segregating tenants by different namespaces inside a submarine, the It was found that some services were not accessible to each other and the submarine was not running properly. I'm not sure about the details of the situation.
BR, Xun Liu On Fri, Sep 30, 2022 at 5:43 PM Xiang Chen <cdmikec...@hotmail.com> wrote: > Hi all > > I am currently conducting a PR review ( > https://github.com/apache/submarine/pull/999) and I have found a > multi-tenancy issue about model serving. > > The current serving deployment is based on the `default` namespace, > however the actual serving service we are doing is on a different tenant > service under the operator. So we may need to move the relevant > [seldon-secret.yaml]( > https://github.com/apache/submarine/blob/master/submarine-serve/installation/seldon-secret.yaml) > file inside the operator for implementation (I have already created an > issue about this https://issues.apache.org/jira/browse/SUBMARINE-1332). > > We have `submarine-cloud-v2` and v3 under the current master branch. There > seems to be a lack of progress on the progress of the operator upgrade. > So I thought I'd ask if we should base all our new issue/PR changes on v3 > and migrate the operator deployment to v3 from recently after testing and > validation? >
