-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Onboarding rbohne to zero #149
Comments
Duplicate of: operate-first/apps#432 FIX pending Re-purposing this ticket as an onboarding for your namespace. namespace is: See this template for a template in what kind of info we need |
Questionnaire
|
/hold I'm not sure if we want personal demo namespaces and one-man teams on the zero cluster :) @rbo could you pick a demo that you already have and then work onboarding that to the cluster? Like #113 I'm not sure about the team name in such a case. Maybe the team is the demo maintainers and the team name would be the demo name?! Or if its a workshop, it's similar to the workshop team? |
It is to get experience in that env and later on to promote it to the german SA team.
I'm one of the go-to person around openshift for the German SA team, from my point of view it makes sense to know how it works and how it feels from the user perspective. Hope that helps to understand my viewpoint. |
Thanks for the background. Is http://www.openshift-anwender.de "just" a website app? If you're good with the kind of SLA we provide for the zero cluster open-infrastructure-labs/ops-issues#32 (production cluster) we could target this as a first onboarding example? I'd suggest naming the group and namespace |
Oh, and you can start the onboarding yourself by following option 2 in https://www.operate-first.cloud/users/support/docs/onboarding_to_cluster.md |
I agree -- let's avoid adding individual usernames as team names, maybe this should be better reflected in the onboarding template. |
Why dont we create a group 'sa-dach' with Robert as the goto/proxy/first? Deploying http://www.openshift-anwender.de seems to be a good idea, it will give us some insides on how 'content creators' will fit into our GitOps'ish workflows. And (I guess) the website will show a seasonality, using HPA and analysing metrics might be a nice project to come up with a little bit more cleaver pod autoscaler that is analysing traffic on the DPU and ..... |
sa-dach group sounds good. openshift-anwender is wordpres with an MySQL backend and persistend storage. So how a legacy application fit into gitops :-) |
So, let's sum it up again:
Did I miss anything? 👍 If we can proceed with this setup. |
ACK. @rbo do you want to go through creating the onboarding PRs or shall we (@tumido && @HumairAK :P) |
Feel free to create the PRs, I will take a look over the PR's to learn :-) |
Describe the bug
After login into the zero cluster with my Red Hat account, I was able to create a project/namespace without any quotas or limitation.
To Reproduce
Steps to reproduce the behavior:
Expected behaviour
Can login but can not create a project/namespace.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
It looks like the self-provisioners is still assigned to the group system:authenticated:oauth
[1] https://docs.openshift.com/container-platform/4.7/applications/projects/configuring-project-creation.html#disabling-project-self-provisioning_configuring-project-creation
The text was updated successfully, but these errors were encountered: