goharbor/harbor

How to expose harbor with the Openshift route

Open

#15,583 opened on Sep 13, 2021

View on GitHub
 (5 comments) (0 reactions) (1 assignee)Go (28,490 stars) (5,235 forks)batch import
help wantedkind/requirement

Description

Is it possible to use the Openshift routes instead of ingress to expose harbor services?

As far as I see, expose.type can be:

  1. ingress
  2. clusterIP
  3. nodePort
  4. loadBalancer

Contributor guide

Tech stack
gokubernetesdocker
Domain
infrastructuredevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of Harbor Helm chartKnowledge of OpenShift routes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the Harbor Helm chart, specifically the templates that handle expose.type. The expose.type values are defined in values.yaml. Add support for OpenShift Route by creating a new template or modifying the ingress template to conditionally create Route resources when expose.type is set to 'route' or similar. Check the OpenShift documentation for Route API. Consider adding a new value for expose.type and a template for Route. There is a related comment in the issue suggesting the use of Route. Also look at the existing code in the 'templates' directory for ingress and consider adapting it for Route.