-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Customization of ssh-privatekey and ssh-publickey for SSHKeyPair #92
Comments
#91 addresses similar needs. Perhaps this feature request should be folded into that one? |
That sounds reasonable! Currently, our capacities to work on this project are limited, so PRs are always welcome. |
@jkupferer I am currently attempting to work on #91. I would like to address this issue together. Can we discuss the design aspect in #91? |
@mrchypark Sorry for having missed your comment for so long. Is this something you are still looking at? |
@jkupferer No. I was also busy with other things, so I couldn't keep up with it even though it was necessary. We can restart the conversation if needed. |
- Add ability set privateKeyField and publicKeyField to set secret fields to store SSH private/public keys. - Resolves mittwald#92
Is your feature request related to a problem? Please describe.
For compatibility with using deploy keys with ArgoCD it is necessary to be able to generate SSH keypair secrets with data
sshPrivateKey
rather than the defaultssh-privatekey
.Other use cases may also require the SSH public and private keys to use custom data names.
Describe the solution you'd like
Perhaps add
spec.sshPrivateKeyDataName
andspec.sshPublicKeyDataName
to SSHKeyPair custom resource to allow overriding the defaults?Describe alternatives you've considered
I've been unable to come up with a reasonable alternative.
Additional context
n/a
The text was updated successfully, but these errors were encountered: