Skip to content
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

Closed
rawlingsj opened this issue Dec 11, 2018 · 11 comments
Closed

add support for harbor registry #2489

rawlingsj opened this issue Dec 11, 2018 · 11 comments

Comments

@rawlingsj
Copy link
Member

see https://www.cncf.io/blog/2018/07/31/cncf-to-host-harbor-in-the-sandbox/

/kind enhancement
/assign rawlingsj

@SyCode7
Copy link

SyCode7 commented Feb 19, 2019

Is this feature now available ?

@fjudith
Copy link

fjudith commented Apr 17, 2019

+1

Harbor also support LDAP and OIDC for AuthN/AuthZand
It is also fully manageable via REST API.

@leosunmo
Copy link

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?

@athilaelhuno
Copy link

Hello, any news about this request

@bbhuston
Copy link

+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).

@marthydavid
Copy link

+1

@jenkins-x-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

@jenkins-x-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

@jenkins-x-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

@jenkins-x-bot
Copy link
Contributor

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

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.

@bagutzu
Copy link

bagutzu commented Sep 30, 2021

+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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests