operator-framework / operatorhub.io Goto Github PK

Uploading the attached files leads to owned CRDs not being recognized by the editor even though they are correctly placed and formatted.

minio-operator.zip

Uploading CRDs with spec.versions instead of spec.version leads to CRD forms being pre-populated without the API version, example here: https://github.com/jetstack/cert-manager/blob/b8bd8dc665dae418a7c514cc414befac272cdb15/deploy/manifests/00-crds.yaml#L1364

IMHO the UI should be populated using the last entity in that list.

it would be nice to search on software license aka for GPL/APL vs private/proprietary license operators.

currently you must click at least 3 times to find out what the license is
example: https://operatorhub.io/operator/elastic-cloud-eck > https://github.com/elastic/cloud-on-k8s > https://github.com/elastic/cloud-on-k8s/blob/master/LICENSE.txt

if License was a metadata tag, it could be exposed here on the operator's landing page along with other pertainent information:

requested by @gregswift @logdna

Hi, would it be possible to filter operators with license? so perhaps, operators which content and which operated service has a osi/fsf approved known open source license? that would be great! :)
Or if it is NOT opensource, simply flag it that way?

operator-framework/operator-sdk#4691

Would be very helpful to make small edits inline before copying.

Thanks

Describe the bug
operatorhub.io sometimes instructs user to use old OLM version
Cause: I suspect the client-side github call fails, and the fallback version is hardcoded to 0.11.0 in frontend/src/redux/operatorsReducer.ts

What did you do?

1. Click any operator
2. Click install.

What did you expect to see?
Instructions should suggest installing OLM 0.14.1 (or latest current release)

What did you see instead?
Instructions suggest installing OLM 0.11.0, which causes errors in latest kube

$ curl -sL https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.11.0/install.sh | bash -s 0.11.0

Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply

The CustomResourceDefinition "clusterserviceversions.operators.coreos.com" is invalid: 

* spec.validation.openAPIV3Schema.properties[spec].properties[install].oneOf[0].properties[spec].properties[image].type: Forbidden: must be empty to be structural
* 
...

cc @lwan-wanglin

Describe the bug
The command 'operator-sdk olm-catalog gen-csv' in the section Create Catalog Data with the Operator SDK has been removed from the operator-sdk in version 0.15.0. Yet the Page on Operatorhub.io still references the command.

I ran npm run-script build and found these unreported deprecation issues. I hope it is helpful to get them documented.

npm WARN deprecated @patternfly/[email protected]: WARNING: @patternfly/patternfly-next has been deprecated and replaced by @patternfly/patternfly. Please install it with npm install @patternfly/patternfly.
npm WARN deprecated @patternfly/[email protected]: Please use react-core 2.0 - this build contains breaking changes
npm WARN deprecated [email protected]: use String.prototype.padStart()
npm WARN deprecated [email protected]: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated [email protected]: core-js@<2.6.8 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Example: "I have an issue when (...)"

I have an issue when I try to access the community operators in my OpenShift deployment when my OpenShift is deployed with IPV6 support. The operators list is empty because operatorhub.io does not have an AAAA for IPV6 network traffic.

Can we enable IPV6 support for this site.

➜  auth git:(master) ✗ host -t AAAA operatorhub.io
operatorhub.io has no AAAA record

Hi, the page refers to a 2016 blog post and to the code specific line in the example operator memcached_controller.go. Both links are wrong now.

There's a link in this page named "submitting your operator " which points to a non existent resource:
https://github.com/operator-framework/community-operators/blob/master/docs/contributing.md#submitting-your-operator

so users get 404 instead of instructions on how to submit an operator.

Possibly this needs to be changed but no idea what should be the new link:
https://github.com/operator-framework/operatorhub.io/blob/master/frontend/src/utils/documentationLinks.ts#L4

Structural Schemas for CRDs were described in a Kubernetes blog back in June.

It would be really great if the CRD presentation showed the information that the new schema provides so that users can make more intelligent decisions regarding their input and what is acceptable. This schema data is already being put into the bundles that are being consumed, it just needs to be presented. Perhaps a first step would be just to show that it exists and give a link to the CRD in the git repo to check it out.

As an example of the schema input already available:
https://github.com/operator-framework/community-operators/blob/master/upstream-community-operators/ibmcloud-operator/ibmcloud_operator_v1alpha1_service.crd.yaml

How that CRD is currently presented:
https://operatorhub.io/operator/ibmcloud-operator

An Operator is an application-specific controller that extends the Kubernetes API to create, configure, and manage instances of complex stateful applications on behalf of a Kubernetes user. It builds upon the basic Kubernetes resource and controller concepts but includes domain or application-specific knowledge to automate common tasks.

From the introduction of operators (quote above taken from there), operators have had a lot of great potential.

What has not been part of being an operator is the way it is installed/updated/etc. The current OperatorHub implementation requires of the use of OLM. But, operators can be installed and have their lifecycles managed with varying different tools. In it's simplest form, raw Kubernetes manifests and kubectl could be used. This idea could be used with a GitOps workflow, too.

Since this is OperatorHub, and not OLMHub, can it be made so that all operators can be listed no matter the mechanism used to install them.

We have some automation that would make it easy to maintain a catalog container automatically with our own operators instead of manually creating PR's against https://github.com/operator-framework/community-operators. Could the website add support for additional catalogs?

I think terminal recording is a great way to show a tutorial and asciinema.org is really cool.

Try one that I've made - https://asciinema.org/a/kCziF0feQD9qmNioLUSAZNoEm?speed=2&autoplay=1

See how you can pause and copy-paste the text from the player directly because it actually renders these as html.

Here is asciinema player embedding options here - https://asciinema.org/docs/embedding

Do you think it makes sense to add it so operators could use it?
I wish github would also support it in their Markdown...

Describe the bug

Dragging and dropping a directory on the new bundle editor has no effect when using Firefox.

What did you do?
A clear and concise description of the steps you took. For example, steps to reproduce the behavior:

1. Go to https://operatorhub.io/packages#
2. Drag and drop valid directory (works in chrome)
3. See error

What did you expect to see?

The upload working.

What did you see instead?

No message, no response, no effect.

Additional context

Firefox version: 78.0.1 (64-bit)

OperatorHub.io currently expects a flat directory structure of an Operator bundle that holds all CRDs, CSVs and the package.yaml.
Since the rest of the Operator Framework moves to the nested bundle format, so should OperatorHub.io

I tried to run the Dockerfile and ran into errors. This made me wonder if it had been moved to an S2I build method. I was successful running this S2I build in my OpenShift cluster. Perhaps this is a bit of documentation in the readme and removing the Dockerfile? If that is an approved direction, I'll submit it.

oc new-app registry.access.redhat.com/ubi8/nodejs-10:latest~https://github.com/operator-framework/operatorhub.io.git

Describe the bug
OperatorHub.io displays a blank page

What did you do?

1. Go to https://operatorhub.io in a modern web browser (Chrome, Firefox, Safari)

What did you expect to see?
The main page of OperatorHub.io
No other pages work either.

What did you see instead?
A blank webpage

Additional context
It appears that the https://operatorhub.io/static/app~748942c6.e6a354.bundle.js contains HTML and not JavaScript code. This was validated by viewing the source of the https://operatorhub.io/static/app~748942c6.e6a354.bundle.js and the fact Chrome interprets it as type of text/html.

Strangly, if you navigate to https://operatorhub.io/static/app~748942c6.e6a354.bundle.js the webpage is no longer blank and functions appropriately. However, a different bundle.js is called out if you view the source there.