### Summary After configuring, validating and activating the Harbor integration on a project/group level, the `Harbor Registry` submenu entry of the `Packages and registries` menu does not appear on our installation. (GitLab EE 15.7.5). Navigating to `domain/group/project/-/harbor/repositories` directly does not work, either, so it seems to be more than just a UI problem for us. The integration of the new environment variables for CI/CD jobs works just fine, though, we can push/pull from Harbor in our pipelines. ### Steps to reproduce 1. Create a new repository. 2. Configure the Harbor integration from the project's Integration settings menu. 3. (Optional) Validate the entered configuration 4. Save the entered configuration 5. UI doesn't update. Direct navigation to `/-/harbor/repositories` does not work, either. ### Example Project Strangely, on gitlab.com the integration of the same Harbor instance works just fine. ### What is the current *bug* behavior? - The API calls for validating the configured data needed to connect to Harbor gets logged and responded on Harbor's side just fine - Afterwards, no more API calls are issued from my GitLab instance - No change in the project's UI can be observed ### What is the expected *correct* behavior? Similar to the behaviour observable on gitlab.com - validation of the configured data works - when saving, additional API calls should get received by Harbor - It’s supposed to be a subitem of the `Packages and registries` entry in the vertical navbar on the group or repository level called `Harbor Registry`. #### Results of GitLab environment info The instance where this issue can be observed is deployed on a Kubernetes cluster, using the GitLab Operator `v0.15.5` using GitLab's Helmchart `v6.7.5` which deploys GitLab `v15.7.5` <details> <summary>Expand for output related to GitLab environment info</summary> <pre> System information System: Proxy: no Current User: git Using RVM: no Ruby Version: 2.7.7p221 Gem Version: 3.2.33 Bundler Version:2.3.15 Rake Version: 13.0.6 Redis Version: 6.0.16 Sidekiq Version:6.5.7 Go Version: unknown GitLab information Version: 15.7.5-ee Revision: 677cf66582b Directory: /srv/gitlab DB Adapter: PostgreSQL DB Version: 13.8 URL: https://REDACTED HTTP Clone URL: https:/REDACTED/some-group/some-project.git SSH Clone URL: git@gREDACTED:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: no Using Omniauth: no GitLab Shell Version: 14.14.0 Repository storages: - default: tcp://gitlab-gitaly-0.gitlab-gitaly.gitlab.svc:8075 GitLab Shell path: /home/git/gitlab-shell </pre> </details> #### Results of GitLab application Check <!-- Input any relevant GitLab application check information if needed. --> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> gitlab-shell self-check failed Try fixing it: Make sure GitLab is running; Check the gitlab-shell configuration file: sudo -u git -H editor /home/git/gitlab-shell/config.yml Please fix the error above and rerun the checks. Checking GitLab Shell ... Finished Checking Gitaly ... Gitaly: ... default ... OK Checking Gitaly ... Finished Checking Sidekiq ... Sidekiq: ... Running? ... no Try fixing it: sudo -u git -H RAILS_ENV=production bin/background_jobs start For more information see: doc/install/installation.md in section "Install Init Script" see log/sidekiq.log for possible errors Please fix the error above and rerun the checks. Checking Sidekiq ... Finished Checking Incoming Email ... Incoming Email: ... Reply by email is disabled in config/gitlab.yml Checking Incoming Email ... Finished Checking LDAP ... LDAP: ... LDAP is disabled in config/gitlab.yml Checking LDAP ... Finished Checking GitLab App ... Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Cable config exists? ... yes Resque config exists? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... skipped (no tmp uploads folder yet) Systemd unit files or init script exist? ... no Try fixing it: Install the Service For more information see: doc/install/installation.md in section "Install the Service" Please fix the error above and rerun the checks. Systemd unit files or init script up-to-date? ... can't check because of previous errors Projects have namespace: ... 2/1 ... yes 6/2 ... yes 6/3 ... yes 6/4 ... yes 4/5 ... yes Redis version >= 6.0.0? ... no Try fixing it: Support for your Redis version 5.0.14 has been deprecated and will be removed soon. Update your Redis server to a version >= 6.0.0 For more information see: doc/administration/redis/index.html#redis-replication-and-failover-using-the-non-bundled-redis Please fix the error above and rerun the checks. Ruby version >= 2.7.2 ? ... yes (2.7.7) Git user has default SSH configuration? ... yes Active users: ... 3 Is authorized keys file accessible? ... skipped (authorized keys not enabled) GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes Elasticsearch version 7.x-8.x or OpenSearch version 1.x ... skipped (Advanced Search is disabled) Checking GitLab App ... Finished Checking GitLab subtasks ... Finished </pre> </details> If more information is needed or you'd need me to take additional steps for debugging, let me know.