New Repo: kn-plugin-operator

[houshengbo]

Use this issue type to request a new repo in knative-sandbox (or
knative, which may require additional discussion).

Repo information

Org: knative-sandbox

Repo: kn-plugin-operator

Purpose (Description):
Knative Operator, as the management tool for Knative components, has given us the capability to manage the lifecycle of Knative. Knative Operator CRs are used to configure everything. The users need to know the definition of each field of the Knative Operator CRDs to leverage configuration options.

This CLI plugin aims to lower the barrier for users to use the Knative Operator, and provides a command interface to access the Kubernetes cluster for Knative management. As well as directly accessing the Knative Operator CRs, the Knative Cluster Admins can use the CLI plugin as well to manage Knative with the Knative Operator.

Sponsoring WG: Client, Operation and user Experience work groups

Actions to fulfill

This area is used to track the repo creation process.
The requestor and sponsoring WG lead should perform the steps listed below and cross out the checkmarks when done.
The TOC is involved only in the TOC Gate steps.

• Add this issue to the TOC project board for review. You are responsible for moving your entry on the board to "Needs Discussion" or "In Progress" as you move forward in this checklist.

You may not be able to use the Projects quick menu on this page. In that case, go to the project board and use the Add cards interface.

• Send a PR adding entries for this repo in /peribolos/knative-sandbox.yaml. Please mind the alphabetical order when adding to a list.
  • Add the repository and a description.
  • Grant Knative Admin the admin privilege.
  • Grant the sponsoring WG the write privilege.

TOC Gate: Once the TOC has approved the above, it will merge and Peribolos will create an empty repository.

• (golang) Send a PR to add aliases for knative.dev/$REPONAME import paths (sample).

• Have a lead from the sponsoring WG bootstrap the Git repository by pushing an
  appropriate "template" repository (basic,
  sample-controller,
  sample-source) to the new repository as
  a git remote. For example:

    git clone https://github.com/knative-sandbox/sample-controller.git
    cd sample-controller
    git remote add newrepo https://github.com/knative-sandbox/$REPONAME.git
    git push newrepo main

• Add your GitHub ID to the OWNERS file for your repo.

• Set up prow for a new repo

• Bootstrap your CI jobs using hack project (look at other sandbox repos for reference)

• Create a sample PR to verify Prow (e.g., edit the boilerplate README)

• Verify that within 24 hours the appropriate branch protections have been applied
  requiring tide to pass before PRs are merged.

• (optional) Send a PR adding the repo to knobots.

[houshengbo]

/assign @rhuss @dsimansk
I need your support and approval to move on with this proposal.

[dsimansk]

+1
It's nice addition to support operator deployments & use.

[rhuss]

+1 from my side, let's move it forward.

[rhuss]

Not done yet.

[evankanderson]

Do we need to do something to move this along?

[evankanderson]

It looks like this is done now. I see 84 PRs committed, including those from knobots, so I think all the steps are done.

/close

[knative-prow-robot]

@evankanderson: Closing this issue.

In response to this:

It looks like this is done now. I see 84 PRs committed, including those from knobots, so I think all the steps are done.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.