Skip to content

Operator Wishlist for OKD #456

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.

Sign up for GitHub

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

Jump to bottom
Closed
LorbusChris opened this issue Jan 5, 2021 · 52 comments
Closed

Operator Wishlist for OKD #456

LorbusChris opened this issue Jan 5, 2021 · 52 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@LorbusChris
Copy link
Contributor

LorbusChris commented Jan 5, 2021 •
edited by vrutkovs
Loading

Operator Wishlist for OKD

Currently Unavailable

Available in Community Catalog

Available in Upstream Catalog
@LorbusChris LorbusChris pinned this issue Jan 5, 2021
@bdlink
Copy link

bdlink commented Jan 9, 2021

OCP 4.6 docs have a section on Metering (missing from OKD docs) that mentions the Metering Operator from OperatorHub. This sounds like a useful operator to add. There is https://operatorhub.io/operator/metering-upstream (which mentions 4.2 version) that refers to https://github.com/kube-reporting/metering-operator but this is no longer under development.
I am not clear which specific operator the OCP document is referencing.

@kanadaj
Copy link

kanadaj commented Jan 15, 2021

Does the upstream rook-ceph operator work? Or does it need additional SCCs?

@bdlink
Copy link

bdlink commented Jan 16, 2021

Please add gitlab operator, see https://gitlab.com/gitlab-org/gl-openshift/gitlab-operator/ It manages the GitLab runner that allows gitlab-based pipelines on OCP (so hopefully OKD). It is not on operatorhub.io
This is used in some redhat blogs as well, see https://www.openshift.com/blog/building-openshift-pipelines-with-gitlab

@chriskuipers
Copy link

chriskuipers commented Jan 18, 2021 •
edited
Loading

I thought it was just us not having access to these operators! But apparently we're not the only ones... I'm here for the popcorn 🍿

@ibotty
Copy link

ibotty commented Jan 20, 2021

Rook-ceph works great if deployed using the openshift-sccs from its examples. It is not using OLM though.

@vrutkovs vrutkovs mentioned this issue Apr 8, 2021
Closed
@OleksandrShtepa
Copy link

Please, add openshift-local-storage https://github.com/openshift/local-storage-operator

@LorbusChris
Copy link
Contributor Author

LorbusChris commented Apr 8, 2021 •
edited
Loading

I've updated the list with the latest suggestions

@msheldyakov
Copy link

KubeVirt Operator now available in community catalog https://github.com/operator-framework/community-operators/tree/master/community-operators/community-kubevirt-hyperconverged

Tekton-Pipelines Operator deprecated and archived. the OpenShift Pipeline Operator lives in the tektoncd/operator upstream repository. https://github.com/tektoncd/operator

@LorbusChris
Copy link
Contributor Author

thanks @msheldyakov, I've updated the list :)

@msheldyakov
Copy link

New item for wishlist https://github.com/openshift/cluster-kube-descheduler-operator
I could not find it in the community and upstream.

@danielchristianschroeter
Copy link

https://github.com/nginxinc/nginx-ingress-operator would be great for OKD, too :)

@ibotty
Copy link

ibotty commented May 26, 2021

We have that great list. What can one do to help getting more operators into the OKD OperatorHub?

@vrutkovs
Copy link
Member

This list can be split in several categories:

  • OCP operators requiring a community version.
    These usually don't apply to upstream k8s, so it needs to be put in the future OKD-specific catalog.
    This would be taken care internally.
  • Other operators:
    Example: nginx-ingress-operator (possibly)
    It needs to be submitted by community members to https://github.com/operator-framework/community-operators.
    If the operator doesn't need any changes (i.e handles SCCs) it can be made available in OKD by submitting to community-operators folder. Otherwise we need to work upstream to have native OKD support in the operator to achieve that.

@binnes
Copy link
Member

binnes commented Jun 4, 2021

New item for Wishlist - Openshift Pipelines (Tekton) - https://github.com/openshift/tektoncd-operator

@vrutkovs vrutkovs mentioned this issue Jun 28, 2021
Closed
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 2, 2021
@vrutkovs
Copy link
Member

vrutkovs commented Sep 3, 2021

/lifecycle frozen

@openshift-ci openshift-ci bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 3, 2021
@vrutkovs vrutkovs mentioned this issue Oct 7, 2021
Closed
@nevidanniu
Copy link

https://docs.okd.io/latest/web_console/odc-about-web-terminal.html
looks like doc for openshift operator "web terminal" occasionally appeared in okd docs, but it would be great to add it to community operators

@vgojayev vgojayev mentioned this issue Feb 18, 2022
Open
@ibotty
Copy link

ibotty commented Jun 3, 2022

openshift/oadp-operator#722 says that oadp is not supported.

@kaovilai
Copy link

kaovilai commented Jun 3, 2022

@ibotty community support is not official support. Our community support ends at OADP 0.5.6 currently.

@dymurray
Copy link

dymurray commented Jun 3, 2022

To be extra clear, OADP is shipped as part of Red Hat official operators. When OADP became supported we stopped maintaining the community version. If someone installs the red hat operator catalog source they will be able to install the latest version of OADP.

@mburke5678 mburke5678 mentioned this issue Jun 3, 2022
Merged
@bdlink
Copy link

bdlink commented Jun 5, 2022

To be extra clear, OADP is shipped as part of Red Hat official operators. When OADP became supported we stopped maintaining the community version. If someone installs the red hat operator catalog source they will be able to install the latest version of OADP.

Unfortunately the Red Hat operator catalog is not accessible to OKD. Stopping supporting the community version means OKD is stuck at the 0.5.6 community version.

@binnes
Copy link
Member

binnes commented Jul 12, 2022

Source for OCP and OKD Operator catalogs are here : https://github.com/orgs/redhat-openshift-ecosystem/repositories

@ibotty
Copy link

ibotty commented Jul 12, 2022

I would certainly like the local storage operator to be in the okd operators. Without this operator it's pretty hard to install rook or openshift monitoring performantly.

@OleksandrShtepa
Copy link

Cert Manager Operator is available now in OKD 4.11. I had install it successful.
GitLab Operator is available, not tried.
GitLab Runner Operator is available, but can not be installed via bug

@vrutkovs
Copy link
Member

Thank you, updated the issue description

@imdmahajankanika
Copy link

Is it possible to add the operator for stackrox (RHACS)?

@shdwchn10
Copy link

Please add to the list ClusterResourceOverride and Sandboxed Containers operators

@kaplan-michael
Copy link

Hey, Can the ODF operator be added to the wish list? https://github.com/red-hat-storage/odf-operator
What needs to be done to support it? It seems it installs fine with OLM(latest from the repo) but fails on pulling registry.redhat.io/openshift4/ose-kube-rbac-proxy:v4.11.0. So that would have to be rebuilt somewhere without a pull secret required.

I'm happy to help get that done.

@vrutkovs
Copy link
Member

vrutkovs commented Oct 26, 2023 •
edited
Loading

What needs to be done to support it?

A public rebuild of all ODF components with a different names/branding (similar to CentOS/RHEL situation). For start we can start with hard fork and then work with ODF team to make sure its useful for both endusers and developers, so that devs would use it as upstream.
This applies to pretty much every operator in this list

@ibotty
Copy link

ibotty commented Nov 6, 2023

https://docs.okd.io/4.14/networking/ingress-node-firewall-operator.html#ingress-node-firewall-operator is also missing outside of RedHat subscriptions.

@kaplan-michael
Copy link

@vrutkovs

A public rebuild of all ODF components with a different names/branding (similar to CentOS/RHEL situation). For start we can start with hard fork and then work with ODF team to make sure its useful for both endusers and developers, so that devs would use it as upstream. This applies to pretty much every operator in this list

Not sure where the hard form should be done(destination) and not sure what the with a different names/branding should be? I don't have the contacts to work with the ODF team to make it a useful upstream for them. I'm happy to help with the work on public rebuilds. pinged you on kubernetes slack with more details.

@Tiriyon
Copy link

Tiriyon commented Jan 8, 2024

Hey, is this issue still in the works?

I am trying to install an operator that seems to be missing:

Is this still missing? is this list still updating?

@margaretjoanmiller
Copy link

Is there a way to add CloudNativePG operator?

@GingerGeek GingerGeek unpinned this issue Feb 27, 2024
@GingerGeek GingerGeek pinned this issue Feb 27, 2024
@stolencode
Copy link

fresh deployment of OKD 4.14, bare metal UPI x86_64. kubernetes-nmstate and metallb operators are missing.

@lfarkas
Copy link

lfarkas commented Apr 25, 2024

Following the working group meeting 5 July 2022, we are hoping to create an OKD community created operator hub catalog. My suggested list of operators to work on first is as follows:

Operators to allow OKD to act as a build system:

• OpenShift Data Foundation (rook / ceph / noobaa) – this is required to install the Project Quay operator available in the community catalog on OKD • Pipelines (Ideally OpenShift pipelines operator, but can use the upstream Tekton operator as it supports OpenShift) • GitOps (Ideally the OpenShift gitops operator, this is lower priority as there is the ArgoCD operator in the community hub)

was there any progress with it? or what is the current situation about it?

@bo0ts
Copy link

bo0ts commented Apr 25, 2024

The OADP Operator operator is no longer available in community (or only an outdated version). The link now redirects to openshift-adp which requires a RedHat subscription.

@0xHexE
Copy link

0xHexE commented Aug 30, 2024

I found some operator sources which can be helpful.

apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: okd-catalog
  namespace: openshift-marketplace
spec:
  displayName: OKD Catalog
  image: 'quay.io/okderators/catalog-index:odf'
  publisher: OKD Pipeline
  sourceType: grpc

Some operator works some not but good start

apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: operatorhubio-catalog
  namespace: openshift-marketplace
spec:
  displayName: Community Operators
  image: 'quay.io/operatorhubio/catalog:latest'
  publisher: OperatorHub.io
  sourceType: grpc

@GingerGeek
Copy link
Member

@0xHexE Would be great to understand what issues you see with the operators.

The catalog source you have listed for okderators is a testing branch (odf) - this won't continue to be updated and may have bad builds pushed to it.

The recommended installation manifest can be found here

We will likely close this issue and move discussion over to the OKDerator project

@guliaka
Copy link

guliaka commented Sep 11, 2024

cilium operator

@llomgui
Copy link

llomgui commented Oct 8, 2024

cilium operator

https://github.com/isovalent/olm-for-cilium

@nate-duke
Copy link

https://github.com/CrowdStrike/falcon-operator

We have a requirement by our security folks to run Crowdstrike on all of our systems. They have a RedHat Openshift Certified (tm) version and some instructions for installing on generic kubernetes so it shouldn't be too terrible. My largest concern is Crowdstrike supporting SCOS (we have a question in to our TAM about this).

@GingerGeek
Copy link
Member

Thank you everyone for your contributions to this discussion.

The OKD WG is now developing + maintaining OKDerators. This Catalog Source will be included by default in OKD soon. This is akin to the "first-party" operators found in OpenShift. An opinionated set of operators, generally from the CNCF landscape, to solve common problems. For example ArgoCD for GitOps, Local Storage Operator for managing LVMs, Rook-Ceph for multi-node storage, etc. These operators are then packaged and distributed within this catalog.

You can see what's currently included here:
https://github.com/okd-project/okderators-catalog-index/tree/release-4.18/catalog

We are looking for volunteers/contributors to help bring across more operators into the catalog (e.g. ODH, OCM) and engage with the upstream projects and relevant RH teams to encourage involvement with the OKD community

For operators that currently only exist in the RedHat Certified/Marketplace - there is no easy home for them currently. If you are interested in seeing any of these operators in OKD it would be interesting to know which operators they are. My understanding is that some of these are not under OSS licenses so it would be for the vendors to engage in that process as well

@ibotty
Copy link

ibotty commented Apr 19, 2025

That's pretty nice. But it would be even better if okderators would also be maintained at least a bit. Is there some documentation on how to contribute? I looked into how it is going to build, but I don't have the time to set up my own cluster (with tekton, etc) to build things. Can one submit a draft PR and let a okd provided cluster test whether it works? That would be pretty nice.

@GingerGeek
Copy link
Member

GingerGeek commented Apr 21, 2025 via email

@titou10titou10
Copy link

titou10titou10 commented Apr 21, 2025 •
edited
Loading

(Sorry @GingerGeek I deleted my previous post as it was way wrong. sorry for that)

Is there some documentation on how to contribute? ... Can one submit a draft PR and let a okd provided cluster test whether it works?

@GingerGeek. @ibotty I'm also looking for this.
I tried to install the "okd pipeline" operator from this catalog but hit a problem related to "StepAction version conversion not enabled..." (to be investigated)
The fact is that the operator deploys tekton pipelines v0.65.5, the "official" RH/OCP pipeline operator deploys v0.68.0 (with operator v1.18.0), the official tekton operator also deploys v0.68.0 (with operator v0.75.0). The current version of tekton pipeline is v0.70.0
I have no idea what are the rule for the okd operator versionning in this catalog. Should it follow RH/OCP operator releases or the base tekton operator release? Is there a governance that describe the policy?
I also have no idea on what to do to propose a PR to upgrade the version of the components of the operator (... to what version?)

ref: https://github.com/tektoncd/operator/releases

@titou10titou10
Copy link

I started a discussion here: https://github.com/okd-project/okderators-catalog-index/discussions/32

@GingerGeek
Copy link
Member

Thanks, I will move the discussion there as this issue is now closed.

@GingerGeek GingerGeek unpinned this issue May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests