-
Notifications
You must be signed in to change notification settings - Fork 786
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
add support for harbor registry #2489
Comments
Is this feature now available ? |
+1 Harbor also support LDAP and OIDC for AuthN/AuthZand |
This is something that will probably stop me from properly using Jenkins X. Is there a nice way to use existing Chartmuseums and Docker registries right now even if it's not a "nice" out-of-the-box experience? |
Hello, any news about this request |
+1 Harbor + JenkinsX integration would be a great feature, specially given the fact that 1) Harbor will soon be able to host other artifacts (i.e., it could be a full Nexus replacement) and 2) the Harbor community is working to completely refactor the app to run natively as Kubernetes CRDs (think Strimzi Kafka Operator etc). |
+1 |
Issues go stale after 90d of inactivity. |
Stale issues rot after 30d of inactivity. |
Rotten issues close after 30d of inactivity. |
@jenkins-x-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. |
+1 In a baremetal scenario, the helm charts are basically impossible to store easily, thus making the cluster recovery a very time-consuming and tough job. |
see https://www.cncf.io/blog/2018/07/31/cncf-to-host-harbor-in-the-sandbox/
/kind enhancement
/assign rawlingsj
The text was updated successfully, but these errors were encountered: