Uploaded image for project: 'Operator Runtime'
  1. Operator Runtime
  2. OPRUN-3808

Create proposal for insights checks and reports

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • None
    • None
    • None
    • None
    • None

      Propose solution to use the same base code and logic to perform checks, so that we can gain insights into how users are adopting the solution, similar to what was done in the first POC:
      ➡️ https://github.com/openshift/operator-framework-operator-controller/pull/289

      Examples:

      ## Packages with SemVer-Based Channel Naming

| Catalog     | Total Packages | % Using SemVer | Total Using SemVer | 
|-------------|----------------|----------------|--------------------|
| certified   | 146            | 15.07%         | 22                 | 
| community   | 256            | 11.72%         | 30                 | 
| marketplace | 38             | 2.63%          | 1                  | 
| redhat      | 130            | 56.92%         | 74                 | 

      ## Packages with Channels Following `candidate/fast/stable` Naming

| Catalog     | Total Packages | % Following Conventional | Total Following Conventional | 
|-------------|----------------|--------------------------|------------------------------|
| certified   | 146            | 48.63%                   | 71                           | 
| community   | 256            | 32.42%                   | 83                           | 
| marketplace | 38             | 52.63%                   | 20                           | 
| redhat      | 130            | 76.15%                   | 99   
      ## Channel Edge Graph Usage (skipRange, replaces, skips) by Package

| Catalog     | Total Packages | % of With replaces | % of With skipRange | % of With skips | Total With replaces | Total With skipRange | Total With skips | 
|-------------|----------------|--------------------|---------------------|-----------------|---------------------|----------------------|------------------|
| certified   | 146            | 26.03%             | 21.92%              | 17.12%          | 38                  | 32                   | 25               | 
| community   | 256            | 83.98%             | 11.72%              | 7.81%           | 215                 | 30                   | 20               | 
| marketplace | 38             | 42.11%             | 15.79%              | 15.79%          | 16                  | 6                    | 6                | 
| redhat      | 130            | 73.08%             | 76.15%              | 45.38%          | 95                  | 99                   | 59               |

       

      Acceptance Process

      • Submit the Pull Request (PR) along with the proposal to the team.
      • Demonstrate the proposal to team members for their review and feedback.
      • If the proposal is accepted, the task will be considered done.
      • If the proposal is not accepted, necessary adjustments will be made or it will be closed accordingly.

              rh-ee-cmacedo Camila Macedo
              rh-ee-cmacedo Camila Macedo
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: