You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 12, 2024. It is now read-only.
// For the ssh authorization of the GitSource, the secret is expected to contain `data.ssh-privatekey` and `data.ssh-knownhosts` for the ssh privatekey and the host entry in the known_hosts file respectively.
. However, this limitation may prove restrictive, particularly for scenarios that require Git-based authentication. Expanding rukpak's capabilities to encompass a broader spectrum of authentication methods, such as Kerberos, JWT, OAuth, would be helpful.
The text was updated successfully, but these errors were encountered:
varshaprasad96
changed the title
Handle more authentication options
Support more authentication options
Oct 11, 2023
Do you want to cover container registry authentication with this issue or create a separate one for it? This is often done with a kubernetes.io/dockerconfigjson secret.
This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.
At present, rukpak exclusively supports SSH-based authentication, as indicated in the code here:
rukpak/api/v1alpha1/bundle_types.go
Line 134 in 05f3afd
The text was updated successfully, but these errors were encountered: