Onboard ODH DataScience cluster to Operate First

open-services-group / scrum

SCRUM issues and user stories

GNU General Public License v3.0

0 stars 2 forks source link

Onboard ODH DataScience cluster to Operate First #22

Closed durandom closed 1 year ago

durandom commented 2 years ago

The cluster will be added to the operate first processes and infrastructure. The DS team will keep cluster-admin privileges. The goal is to understand a gap in developing ODH components in a "managed" cluster.

@HumairAK please complete the acceptance criteria list

[ ] add cluster to RHACM
[ ] add Operate First SSO to cluster
[ ] deploy os-c JupyterHub
[ ] add monitoring

the current cluster is in AWS and contains GPUs, similar to the os-c clusters

durandom commented 2 years ago

cc @MichaelClifford @erikerlandson

MichaelClifford commented 2 years ago

Thanks @durandom !

Do we need to "deploy os-c JupyterHub"? This cluster all ready has an ODH instance running with JupyterHub

schwesig commented 2 years ago

/kind onboarding /area monitoring

sesheta commented 2 years ago

@schwesig: The label(s) kind/onboarding, area/monitoring cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/open-services-group/scrum/issues/22#issuecomment-1202719590): >/kind onboarding >/area monitoring Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

HumairAK commented 2 years ago

Feedback:

Onboard Cluster docs non existed
ACM access point should be linked service (Service catalog?)
Docs should give alternative suggestion to auth if it cannot be dependent on infra identitatem

schwesig commented 1 year ago

mentioned to @codificat

sesheta commented 1 year ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

sesheta commented 1 year ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

sesheta commented 1 year ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

sesheta commented 1 year ago

@sesheta: Closing this issue.

In response to [this](https://github.com/open-services-group/scrum/issues/22#issuecomment-1476729326): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.