Open
Description
The Integration with Mozilla's sops](https://carvel.dev/kapp-controller/docs/v0.48.x/sops/) docs jumps straight into a how-to instructions with no high level explanation of how the the integration works. The docs currently assume the reader already knows kapp-controller and Mozilla SOPS.
The SOPS doc page should have a small section added at the start of the doc that explains at a high level how the integration work. parts of this section are:
- brief explanation of mozilla sops
- brief explanation of the fetch / template / deploy life cycle of kapp-controller and where SOPS integrates into the lifecyle
- Steps of the workflow for adding a secret via SOPS, the steps should not explain the how just the main steps. The rest of the doc will explain how to accomplish the steps. We are trying to help the users understand the sequence of steps they need to go through.
- Steps of the workflow for updating a secret after it has been added, only high level steps not how to do it. The how should be explained in the rest of the doc.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Prioritized Backlog