Skip to content
This repository was archived by the owner on Jul 30, 2021. It is now read-only.

Add upstream Knative Serving operator#1146

Merged
J0zi merged 1 commit into
operator-framework:masterfrom
aliok:add-knative-serving
Jan 28, 2020
Merged

Add upstream Knative Serving operator#1146
J0zi merged 1 commit into
operator-framework:masterfrom
aliok:add-knative-serving

Conversation

@aliok
Copy link
Copy Markdown
Contributor

@aliok aliok commented Jan 23, 2020

Signed-off-by: Ali Ok aliok@redhat.com

Thanks submitting your Operator. Please check below list before you create your Pull Request.


Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.


New Submissions

Updates to existing Operators

  • Is your new CSV pointing to the previous version with the replaces property?
  • Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
  • Have you tested an update to your Operator when deployed via OLM?
  • Is your submission signed?

Your submission should not

  • Modify more than one operator
  • Modify an Operator you don't own
  • Rename an operator - please remove and add with a different name instead
  • Submit operators to both upstream-community-operators and community-operators at once
  • Modify any files outside the above mentioned folders
  • Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

  1. Description about the managed Application and where to find more information
  2. Features and capabilities of your Operator and how to use it
  3. Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

  • Human readable name and 1-liner description about your Operator
  • Valid category name1
  • One of the pre-defined capability levels2
  • Links to the maintainer, source code and documentation
  • Example templates for all Custom Resource Definitions intended to be used
  • A quadratic logo

Remember that you can preview your CSV here.

--

1 If you feel your Operator does not fit any of the pre-defined categories, file a PR against this repo and explain your need

2 For more information see here

@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 23, 2020
@openshift-ci-robot openshift-ci-robot added kubernetes-operator An Operator targeting OperatorHub.io size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 23, 2020
@aliok
Copy link
Copy Markdown
Contributor Author

aliok commented Jan 23, 2020

WIP until knative/serving-operator#263 is merged.
UPDATE: Community reviewed the OLM metadata and it is merged.
cc @houshengbo @jcrossley3

@houshengbo
Copy link
Copy Markdown

@aliok knative/serving-operator#263 is merged.

@aliok aliok changed the title [WIP] Add upstream Knative Serving operator Add upstream Knative Serving operator Jan 24, 2020
@aliok aliok marked this pull request as ready for review January 24, 2020 07:30
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 24, 2020
@aliok
Copy link
Copy Markdown
Contributor Author

aliok commented Jan 24, 2020

cc @J0zi @dmesser

@J0zi J0zi self-assigned this Jan 24, 2020
@aliok aliok force-pushed the add-knative-serving branch from 4ea1dc5 to 1f13f42 Compare January 24, 2020 13:30
Signed-off-by: Ali Ok <aliok@redhat.com>
@aliok aliok force-pushed the add-knative-serving branch from 1f13f42 to b691b8d Compare January 28, 2020 08:02
@J0zi J0zi merged commit 54a3d33 into operator-framework:master Jan 28, 2020
@aliok aliok deleted the add-knative-serving branch January 28, 2020 13:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

kubernetes-operator An Operator targeting OperatorHub.io size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants