4n4nd/odh-moc-support

This repo should serve as a central source for reporting issues with ODH components on MOC.

Operate First Support

Website: https://www.operate-first.cloud/

GitHub Support Repository: https://github.com/operate-first/support

For any questions, concerns, and/or requests, please use the appropriate Issue Template to open an issue on our GitHub. If no template fits your requirement, then please make a regular GitHub issue here.

End User Support

We have a community slack channel where we post announcements, general information, and more. If you have any questions, feel free to post a message to the #support channel.

MOC Environment

The Operate First initiative currently manages two clusters within the MOC environment.

• Zero cluster for all user workloads
• Infra cluster for cluster management, housing ACM and ArgoCD

Please create an issue here if you would like to use a cluster. Note that unless you want to use ACM or operate ArgoCD, you are likely looking for access to the Zero cluster.

Managed Services

Operate First manages various applications and services in the environments listed above. These services are accessible to the general public, and their availability dashboards can be found here.

Note: Access to monitoring and dashboards (i.e. Prometheus and Grafana) is currently restricted, pending discussions on EULAs and data licensing. If you need to access these services in the meantime, please make an issue. We will do our best to accommodate your request.

• Open Data Hub

  • We manage a deployment of Open Data Hub (ODH) on the MOC Zero cluster
  • Read more about our deployment of ODH and access our dashboard

• Kubeflow

  • We deploy a selection of Kubeflow components on the MOC Zero cluster
  • Read more about our deployment of Kubeflow and access our dashboard

• ArgoCD

  • We manage a multi-tenant deployment of ArgoCD on the MOC Infra cluster
  • Anyone can be onboarded to this ArgoCD instance and use it to deploy to any cluster managed by Operate First
    • Before being onboarded to ArgoCD, you must be onboarded to the OCP cluster you wish to deploy your applications on
    • Request access to an OCP cluster by filing an issue here and ArgoCD by filing an issue here
  • Console: https://argocd.operate-first.cloud
  • Monitoring: https://grafana-route-opf-monitoring.apps.zero.massopen.cloud/d/97AYZMTGk/argocd?orgId=1

• Observatorium

  • We have an instance of Observatorium currently being used to provision Thanos and Loki
  • Thanos enables long term storage for Prometheus (deployed by ODH)
    • Anyone can enable their applications deployed on Zero cluster to be monitored by this Prometheus instance
    • To do so, follow the instructions here and make a pull request against this repo
  • Loki is used to query logs; click here to learn more about sending or retrieving logs using Loki
  • Thanos: http://thanos-query-frontend-opf-observatorium.apps.zero.massopen.cloud
  • Monitoring: https://grafana-route-opf-monitoring.apps.zero.massopen.cloud/dashboards/f/VYns1DlGz/thanos

• Cluster Logging Operator

  • We deploy the Cluster Logging Operator (CLO) with Elasticsearch and Kibana on the MOC Zero cluster
  • Anyone who has been onboarded to the Zero cluster can access their application logs via Kibana
  • You can also curl directly to Elasticsearch from this route, but you will need to provide your OCP bearer token

• Openshift Container Storage

  • We deploy the Openshift Container Storage (OCS) operator on the MOC Zero cluster
  • OCS provides both persistent volumes and S3 compatible object storage via Rook Operator
  • Users can deploy their own S3 buckets via ObjectBucketClaims - see here for details

• Dex OIDC Provider

  • We manage an instance of Dex on the Zero cluster; we are working towards using Dex to provide authentication for some of our services
  • Our Dex instance can also be used to drive authentication for other users. While documents are not yet available for this, experienced users can find the configurations here

odh-moc-support's Issues

test

Questionnaire

Kafka Topic

1. Topic names:

2. Topic partitions:

   Default: 3

3. Topic replicas:

   Default: 2

4. Topic retention period:

   Default: 6 hours (21600000ms)

5. Topic Configuration:

   Default: None

Kafka Users

1. User names:

2. Topic access:

   Default: Above requested topics

3. Consumer group ids:

   Default: Same as topic names

4. Your GPG key or contact:

---

If you don't want to wait for the maintainers to notice this issue, you can do the changes yourself. Please follow the Add Kafka Topics guide.