-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
-
SECFLOWOTL-114 - Making Tekton Chains First-Class Citizen of OSP with Default Integrations
-
-
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
- Customer wants to use Chains
- 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
- duplicates
-
SRVKP-3556 Add sane defaults to chains
- On QA