Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-3210

TektonChain Default Configuration

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Tekton Chains
    • None

      Epic Goal

      • Provide a default TektonChain configuration that OOTB that covers the majority of customer use cases

      Why is this important?

      • Customers new to chains and signing will struggle with terminology to configure chains successfully. Chains should just be a bring your signing-secret and it works type of thing

      Scenarios

      1. Customer wants to use Chains
      2. Customer reads docs about configuration and gets frustrated

      Acceptance Criteria (Mandatory)

      • Default configuration works on the box for taskrun, pipelinerun and OCI image signing

      Previous Work (Optional):
      As a data point here is my current configuration:

       

      
      

      apiVersion: operator.tekton.dev/v1alpha1
      kind: TektonChainmetadata:
      name: chain
      spec:
      targetNamespace: openshift-pipelines
      artifacts.taskrun.format: in-toto
      artifacts.taskrun.storage: oci
      artifacts.taskrun.signer: x509
      artifacts.oci.storage: oci
      artifacts.oci.format: simplesigning
      artifacts.oci.signer: x509
      transparency.enabled: true

       

       

              jkhelil abdeljawed khelil
              gnunn@redhat.com Gerald Nunn
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: