Make W&B Operator available in Operator Hub

[vijay-wandb]

Description

Today: Customers have to install the Operator via Helm Chart.

Expectations: Customers can install the Operator from the Operator Hub.

[vijay-wandb]

Mike S had a chat with some of his contacts at Redhat who shared this documentation to contribute to community operator: Community operators - Community operators

[vijay-wandb]

Marc-Steffen Kaesz

https://catalog.redhat.com/search?searchType=containers&partnerName=Red%20Hat&p=1&prod[…]Red%20Hat%20Universal%20Base%20Image%209&architecture=amd64

podman pull registry.access.redhat.com/ubi9/ubi-micro:9.4-13

podman pull registry.access.redhat.com/ubi9-minimal:9.4-1194

podman pull registry.access.redhat.com/ubi9:9.4-1181.1724035907
Micro - Designed for applications that contain their own dependencies (Python, Node.js, .NET, etc.)

The absolute smallest image you can build from

No package manager which makes it smaller

Buildah is recommended instead of a Dockerfile

Minimal - Designed for applications that contain their own dependencies (Python, Node.js, .NET, etc.)

Minimized pre-installed content set

No SUID binaries

Minimal package manager (install, update and remove)

Standard - For any application that runs on RHEL

Unified, OpenSSL crypto stack

Full YUM stack

Includes useful basic OS tools (tar, gzip, vi, etc.)

[vijay-wandb]

Marc-Steffen Kaesz
Volkswagen will only migrate to Operator when available in Operator hub.

[abhinavg6]

https://docs.redhat.com/en/documentation/openshift_container_platform/4.4/html/operators/olm-understanding-operatorhub#olm-understanding-operatorhub

[velotioaastha]

Kubernetes OperatorHub - k8s-operatorhub/community-operators#5077
Red Hat OpenShift Ecosystem - redhat-openshift-ecosystem/community-operators-prod#5300

[abhinavg6]

CI requirements doc from Aastha - https://docs.google.com/document/d/1WcVwkpyStLwJpkmPXJxOB0OFPDp_tNsqXuS7ETpXC3c/edit

[abhinavg6]

Security context work from @flamarion - wandb/helm-charts#240

[theishshah]

Wanted to note a few things Re: Automating release to operator hub

• need gh action automation to run on new release tags
• make bundle and catalog images
• update CSV values with new version info
• update any underlying deps (openshift/olm etc.)(may require creating a process to update deps list at release time)
• Needs github access token to perform following actions (do we have a bot or associated token for automations?)
• create PR against community operator repo within the action (may require manual intervention to merge pr upstream)
• INVESTIGATE: supporting auto-upgrade path instead of full replacement on cluster when getting new operator versions?

[abhinavg6]

@theishshah - As discussed on Thursday, could you please coordinate with @velotioaastha and @amanpruthi on how to go about this work in our repos as they haven't touched our CI stuff yet? Some high-level guidance on a call would be great, and then you could just assist them with admin stuff as needed.
cc @jsbroks