cdenneen
commented
2 years ago @hiddeco looks like this was missed as available parameter to the cli?
https://github.com/fluxcd/flux/pull/2911
❯ flux version
flux: v0.25.3
helm-controller: v0.15.0
kustomize-controller: v0.19.1
notification-controller: v0.20.1
source-controller: v0.20.1
✗ unknown flag: --ssh-key-format
✗ unknown flag: --ssh-keygen-format
Describe the bug
https://fluxcd.io/docs/use-cases/aws-codecommit/
Flux Create Source:
Failed to retrieve list of SSH authentication methods
► applying secret with repository credentials ✔ authentication configured ► applying GitRepository source ✔ GitRepository source updated ◎ waiting for GitRepository source reconciliation ✗ unable to clone: Failed to retrieve list of SSH authentication methods: Failed getting response
Based on some research it has to do with libssh2 upgrade changed the format:
https://github.com/libgit2/pygit2/issues/1013#issuecomment-679200156
It seems in order for this to work with CodeCommit the
-M PEMflag would be necessary when generating the deploy key?Steps to reproduce
Flux Create Source:
► applying secret with repository credentials ✔ authentication configured ► applying GitRepository source ✔ GitRepository source updated ◎ waiting for GitRepository source reconciliation ✗ unable to clone: Failed to retrieve list of SSH authentication methods: Failed getting response
Based on some research it has to do with libssh2 upgrade changed the format:
https://github.com/libgit2/pygit2/issues/1013#issuecomment-679200156
Expected behavior
It seems in order for this to work with CodeCommit the
-M PEMflag would be necessary when generating the deploy key?Kubernetes version / Distro / Cloud provider
Amazon EKS v1.21.5-eks-bc4871b
Flux version
Flux 0.25.3
Git provider
AWS CodeCommit
Container Registry provider
No response
Additional context
No response
Maintenance Acknowledgement
Code of Conduct