This documentation is for Flux (v1) and Helm Operator (v1). Both projects are in maintenance mode and will soon reach end-of-life. We strongly recommend you familiarise yourself with the newest Flux and start looking at your migration path.
For documentation regarding the latest Flux, please refer to this section.
Providing your own SSH key
Flux connects to the repository using an SSH key it retrieves from a
Kubernetes secret, if the configured (
--k8s-secret-name) secret has
identity key/value pair, it will generate new private key.
With this knowledge, providing your own SSH key is as simple as creating the configured secret in the expected format.
create a Kubernetes secret from your own private key:
kubectl create secret generic flux-git-deploy --from-file=identity=/full/path/to/private_key
this will result in a secret that has the structure:
apiVersion: v1 data: identity: <base64 encoded RSA PRIVATE KEY> kind: Secret type: Opaque metadata: ...
(optional) if you created the secret with a non-default name (default:
flux-git-deploy), set the
--k8s-secret-nameflag to the name of your secret (i.e.
Developerpermission can create tags, but not update them.