Ali Ok

We have links to old docs. Need to reach out to CNCF staff for this.

Governance self-assessment template+guide

8

~~Security TAG [has a process](https://github.com/cncf/tag-security#cncf-security-tag-reviews) where they ask for a self-assessment before doing the security reviews as the TAG.~~ ~~We will probably want to have a similar process in the...

CHARTER.md is outdated

2

https://github.com/cncf/tag-contributor-strategy/blob/main/CHARTER.md Does this document need to be maintained? Or, was it just a kick-off thing for the TAG and it is in the repository for historical reasons? Roadmap there is...

TAG CS Contributor ladder

4

In TAG CS repo, - There are ["facilitators"](https://github.com/cncf/tag-contributor-strategy/blob/main/contributor-growth/README.md#facilitators), ["chairs"](https://github.com/cncf/tag-contributor-strategy/blob/main/mentoring/README.md#chairs), ["members"](https://github.com/cncf/tag-contributor-strategy/blob/main/governance/README.md#working-group-members) - Some WGs only have faciliators, some have only chairs, some have only members We should document what these mean...

TAG CS election support process

2

I've recently asked @geekygirldawn and @jberkus to support the Knative community and organize the upcoming steering committee elections. They're kind enough to help, but it would be nice if there's...

KnativeEventing CRD doesn't have proper openApi validation definition

2

**Describe the bug** OpenAPI validation in KnativeEventing CRD is not good. It doesn't provide anything useful. ``` $ kubectl explain knativeeventings.operator.knative.dev KIND: KnativeEventing VERSION: operator.knative.dev/v1alpha1 DESCRIPTION: ``` **Expected behavior** Expected...

OLM metadata for 0.13.1

3

# Issue to be fixed Fixes # ## Proposed Changes * Checking in OLM metadata for 0.13.0 Hold until https://github.com/operator-framework/community-operators/pull/1337 is merged ## Release Note ```release-note NONE ```

Tooling to generate OLM metadata

4

Metadata published to OperatorHub (see https://github.com/knative/eventing-operator/issues/68) is initially created manually. For future versions, we can generate the OLM metadata using the manually created one. Required: - Tooling itself - Documentation

Hide obsolete CRD in OLM

1

As per [OLM docs](https://docs.openshift.com/container-platform/4.3/operators/operator_sdk/osdk-generating-csvs.html#osdk-hiding-internal-objects_osdk-generating-csvs) apply the following annotation on the CSV to hide the obsolete CRD. ``` apiVersion: operators.coreos.com/v1alpha1 kind: ClusterServiceVersion metadata: name: my-operator-v1.2.3 annotations: operators.operatorframework.io/internal-objects: '["my.internal.crd1.io","my.internal.crd2.io"]' ... ```

e2e test script problems when running locally

1

Problems: 1. `OPERATOR_DIR` is a [relative path](https://github.com/knative/eventing-operator/blob/723874e9a1e19ed359e0589b63d7dfa9e388ccde/test/e2e-upgrade-tests.sh#L34) only and that results in strange behavior later, when we `cd` [back](https://github.com/knative/eventing-operator/blob/723874e9a1e19ed359e0589b63d7dfa9e388ccde/test/e2e-upgrade-tests.sh#L121), we won't actually cd back. 2. ~`ko resolve -P` should only...