Just the bare minimum add new text to explain the change to kubecfg
This PR should be reopened as the `jsonnet-gutted` branch, with
commentary removed and slimmed down to just code examples with as little
non-embedded commentary as possible.
This way we can consider reorganizing any pieces that would need to be
redone for example in a hypothetical Jenkins+cdk8s use case document, or
something else like Gitlab+Tanka, or Tekton+kubecfg, or any combination.
If we are going to document outside solutions and proper integrations
with them, then we should probably make their treatments as equal as
possible to avoid showing favoritism.
"release-manifests.yaml" workflow which targets releasing tags that are
labeled as a release, or commits that are pushed on the release branch.
add more detail in jsonnet example section
more text
There might be some overlap with the SOPS/Azure KMS example that Leigh
provided
re-align with #1064
fixup text
substantial rework in introduction
more text that hasn't been in a commit yet
more organization
more commentary
- change links in cli docs to be relative (making mkdocs AND hugo happy)
- run 'make docs'
- fix other links
Signed-off-by: Daniel Holbach <daniel@weave.works>
