edu
edu copied to clipboard
Improve Enforce docs structure
Consider splitting the Enforce docs into sections:
- Enforce overview and architecture maybe
- Signing images, creating sboms
- Link to sigstore projects and docs
- Using signing keys vs. keyless
- Cli vs web
- Agent vs. agentless
- Runtime enforcement vs continuous
- IAM, groups, invite codes
- Signing images, creating sboms
- Getting started with enforce
- Prereqs / compatible k8s distros, versions, etc.
- Signing up
- Signing your images, making sboms
- Setting up chainctl
- Sample policies
- Applying policies to cluster
- Viewing logs
- Chainctl CLI detailed docs. Why do i need this and what does it do that i can’t do with kubectl
- Enforce web UI detailed docs - what do i use this for?
- Separately, quickstart tutorial
Were you thinking these as separate docs? I think we have a number of these on the roadmap but I'll make sure to capture additional ones and capturing proposed headings.
cc @amdawson as this was feedback from him.
All the items listed are either published or in flight with their own tickets, so I will close this out.