Skip to content
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

Closed
rbo opened this issue Mar 25, 2021 · 12 comments · Fixed by operate-first/apps#461
Closed

Onboarding rbohne to zero #149

rbo opened this issue Mar 25, 2021 · 12 comments · Fixed by operate-first/apps#461
Assignees

Comments

@rbo
Copy link
Member

rbo commented Mar 25, 2021

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:

  1. Go to 'https://console-openshift-console.apps.zero.massopen.cloud/search'
  2. Login with our Red Hat Account
  3. Click on create project
  4. Start some bit count mining ;)

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

@tumido
Copy link
Member

tumido commented Mar 25, 2021

Duplicate of: operate-first/apps#432 FIX pending

Re-purposing this ticket as an onboarding for your namespace.

namespace is: rbohne-demo1
Any desired team name @rbo ?
Any secrets you want us to manage?

See this template for a template in what kind of info we need

@tumido tumido self-assigned this Mar 25, 2021
@rbo
Copy link
Member Author

rbo commented Mar 25, 2021

Questionnaire

  1. Team name: rbohne
  2. Desired namespaces:
  • rbohne-openshift-examples
  • rbohne-acme
  • rbohne-demo
  • rbohne-anwendertreffen
  1. Users needing access: [email protected] (RedHat SSO) or my Kerberos Id rbohne

  2. Target cluster:

  • zero for namespaces above.
  • infra to take a look for the upcoming hetzner deployment (If approval needed ask: @goern )
  1. Team or maintainer owned GPG key fingerprint along with a keyserver (OPTIONAL): n/a

@tumido tumido changed the title Can create namespaces/projects without onboarding (cluster: zero) Onboarding rbohne to zero Mar 25, 2021
@durandom
Copy link
Member

durandom commented Mar 25, 2021

/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?

@rbo
Copy link
Member Author

rbo commented Mar 25, 2021

It is to get experience in that env and later on to promote it to the german SA team.
Demo/examples/use cases, I have a couple:

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.

@durandom
Copy link
Member

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 www-openshift-anwender-de (to avoid openshift- prefixes).

@durandom
Copy link
Member

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

@HumairAK
Copy link
Member

I agree -- let's avoid adding individual usernames as team names, maybe this should be better reflected in the onboarding template.

@goern
Copy link
Member

goern commented Mar 26, 2021

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 .....

@rbo
Copy link
Member Author

rbo commented Mar 26, 2021

sa-dach group sounds good.

openshift-anwender is wordpres with an MySQL backend and persistend storage. So how a legacy application fit into gitops :-)

@tumido
Copy link
Member

tumido commented Mar 29, 2021

So, let's sum it up again:

  1. User group: sa-dach with @rbo as the sole member for now
  2. Namespaces:
    • sa-dach-openshift-examples
    • sa-dach-anwendertreffen

Did I miss anything?

👍 If we can proceed with this setup.

@durandom
Copy link
Member

ACK.
@rbo is https://examples.openshift.pub/ is also a webpage that you just want to host, or do you want to host those small examples? First I thought the latter, but if both NS just host webpages, let's do it :shipit:

@rbo do you want to go through creating the onboarding PRs or shall we (@tumido && @HumairAK :P)

@rbo
Copy link
Member Author

rbo commented Mar 31, 2021

Feel free to create the PRs, I will take a look over the PR's to learn :-)

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 a pull request may close this issue.

5 participants