Admin message

GitLab has moved to a new infrastructure on March 28th

As part of this migration, the SSH host keys were upgraded to stronger cryptographic standards. The first time you connect via SSH after the migration, you will see a warning like this:

WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!

This is expected: it does not indicate a security incident.

What to do?

Remove the old host key from your known hosts file by running ssh-keygen -R gitlab.switch.ch.

Your next SSH connection will prompt you to accept the new host key. Verify it matches one of the keys listed in: https://gitlab.switch.ch/help/instance_configuration

Tags

Tags give the ability to mark specific points in history as being important
  • 1.0.10

    90097385 · Put play application secret in a k8s secret · Mar 05, 2026
  • 1.0.9

    10634237 · Remove outdated solr field series2 · Mar 04, 2026
  • 1.0.8

    ddd75bc8 · Adapt kubernetes manifests for the switch to production for the new mongo/kafka/solr servers · Apr 09, 2025
  • 1.0.7

    2ee6b735 · Build based on gitlab components · Dec 05, 2024
  • 1.0.6

    98714fb6 · add filter to swisscollections endpoint · Apr 22, 2024
  • 1.0.5

    172d208a · Use same java versions as before migration, SC-464 · Oct 09, 2022
  • 1.0.4

    128cab04 · Allow new kubernetes hosts · Apr 14, 2022
  • 1.0.3

    0a11bb7d · Remove unused code · Dec 13, 2021
  • 1.0.2

    82d03e67 · Do test-build also for tags · Oct 21, 2021
  • 1.0

    1acb174f · Migrate Ingress, Rename deployment, service, ingress, Move config to conf folder · Oct 21, 2021
  • 1.0.1

    1acb174f · Migrate Ingress, Rename deployment, service, ingress, Move config to conf folder · Oct 21, 2021
  • 0.9

    99160811 · changed port in ingres artefact for sru - now it works · Sep 30, 2021
    0.9