Uploaded image for project: 'Helm'
  1. Helm
  2. HELM-284

Write a how to blog for Certification flow

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Helm
    • AppSvc Sprint 212

      Owner: Architect:

      Story (Required)

      As an OpenShift helm partner I will like to see an example certification flow, so that I have a practical way to interpret the certification flow documentation

      Background (Required)

      A few partners have struggled to follow our documentation. They often do not follow links that are important like links to chart verifier tools. Although we continue to learn and improve as we see those issue a great accelerator that will complement out documentation will be a series or blogs that will allow them to see in practice how they could run their own certification program. This particular story focus on one path of the certification flow, geared toward show partners how to send a chart for certification by providing the report.

      Glossary

      NA

      Out of scope

      Chart only flow

      In Scope

      Report only submission, create report using new executable, create a PR, check catalogue.

      Approach(Required)

      We could take them through some of the use case that apply to that path. For example: partner will like to certify with a specific version of OpenShift different from the latest we always run with. Also, another example could be they will like to certify the charts in a private network not accessible to the public, but only accessible to their customers. Once the use cases are established as an example, we cold then take them through running chart verifier locally creating a report and submitting a PR, we could take them through some of the know issue we have seen, like the Owners file is not populated yet and point them to the partner documentation to create their projects.

      Dependencies

      NA

      Edge Case

      NA

      Acceptance Criteria

      Anyone could follow the blog and to create a successful report only submission.
      Blog is published and accessible to the public

      INVEST Checklist

      Dependencies identified
      Blockers noted and expected delivery timelines set
      Design is implementable
      Acceptance criteria agreed upon
      Story estimated

      Legend

      Unknown
      Verified
      Unsatisfied

              dperaza@redhat.com David Peraza
              dperaza@redhat.com David Peraza
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: