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
* Fixme: Jsonnet is still missing an example.jsonnet
If you test these examples now then you will find
...the example for build doesn't expect or honor any caching, while
there is an easy opportunity to add caching...
Some additional things that need changes to fix them to work
better, or adding more caveats in the tutorial text...
* clarify that "this is CI-ops"
Jsonnet will be 2 examples now, 1- how to copy a configmap in several
repos, 2- how to copy a secret in several repos (the sops/gitops way)
- 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>
This commit adds support for supplying a path to an existing private
key file to both the `flux create secret git` and `flux create source
git` commands.
If a path is given, any private key generation configuration options
are ignored by the manifest generator. The SSH host will however still
be scanned for server keys.
Signed-off-by: Hidde Beydals <hello@hidde.co>
* Set explicit column widths for timetable
No need for old Firefox workaround. It appears fine on FF in 2021
See:
- https://github.com/squidfunk/mkdocs-material/issues/922
- https://github.com/squidfunk/mkdocs-material/issues/118
* Hide TOC right column on migration table page
* SDK->GOTK footnote
* Cross-link admonitions between Roadmap and Timetable
To-do: change structure and file names under migration menu dir when we
move to fluxcd/website
* Add custom heart admonition
* Link to documentated deprecation of apiextensions.k8s.io/v1beta1
CustomResourceDefinition
* Fix caret (^^ underlines short status)
* Initial migration and Support Timetable
Add mkdocs markdown_extensions and sort them alphabetically
Co-authored-by: Stefan Prodan <stefan.prodan@gmail.com>
Signed-off-by: Scott Rigby <scott@r6by.com>
- Switch to batch GPG key creation
- Accurately name the cluster's decryption key
- Suggest password-manager backup
- Optionally cleanup secret key from generating machine
- Optionally commit the public key to the repo for team members
- Document SOPS limitations decryption required for editing / appending fields
Signed-off-by: leigh capili <leigh@null.net>
This was removed by accident in the PR that introduced the new
`manifestgen` packages, and now restored in full glory.
Signed-off-by: Hidde Beydals <hello@hidde.co>
- add make target for generating the install manifests using kustomize
- embed the generated manifests in flux binary
- the install and bootstrap commands default to using the embedded manifests
- download the install manifests from GitHub only if the install/bootstrap version arg is set
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>