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

Make signature key changes to helm repository CRD

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Helm
    • None

      Owner: Architect:

      David Peraza

      Story (Required)

      As an ODC Helm backend developer, I would like the api changes required for key management to be done so that I can implement signature verification in helm backend.

      Background (Required)

      We need to enable HelmChartRepository and ProjectHelmChartRepository CRDs to hold public pgp keys to be able to verify signatures of charts in the repo. There could be one or more keys for multiple charts or chart versions

      Glossary

      NA

      Out of scope

      Implementing ODC backend logic

      In Scope

      NA

      Approach(Required)

      Add a field to the CRDs to hold a list of ConfigMaps. Each ConfigMap will be a pgp key.

      Demo requirements(Required)

      No Demo required

      Dependencies

      NA

      Edge Case

      NA

      Acceptance Criteria

      HelmChartRepositoy can hold a list of pgp keys
      ProjectHelmChartRepository can hold a list of pgp keys
      Documentation: NO
      Upstream: Comments in the CRD
      Downstream: NA

      Release Notes Type: <New Feature/Enhancement/Known Issue/Bug
      fix/Breaking change/Deprecated Functionality/Technology Preview>

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      v

      Legend

      Unknown

      Verified

      Unsatisfied

              kmamgain@redhat.com Kartikey Mamgain (Inactive)
              dperaza@redhat.com David Peraza
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: