Skip to content

Fixed user creation after deployment#18

Open
cwiertniamichal wants to merge 34 commits into
masterfrom
bugfix/user-creation-after-deployment
Open

Fixed user creation after deployment#18
cwiertniamichal wants to merge 34 commits into
masterfrom
bugfix/user-creation-after-deployment

Conversation

@cwiertniamichal

Copy link
Copy Markdown

No description provided.

Before mounting a oneclient by a particular user to a particular provider a check is made if the particular provider actually supports any space own by this user. If not the entry point waits for a support to happen.
Oneclient pod is ready when oneclient properly mounts, oneclient can mount after user spaces are get support. Oneclient readiness is not needed to properly initialize environment, hence this change is justified.
The storageClassName now is the same as default storageClassName of minikube
a consequence of compatibility is new onepanel admin user, that will be a part of a deployment of both 18 and 19 versions. Onepanel rest calls now use this credentials instead of admin account of onezone
now the oneclient pod will no longer hang in Termination state
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants