Skip to content

Products

Featured Pages

Developer Tools

For partners

Latest Updates

  • featurecompute-engine

    Start collecting basic VM performance metrics

    Section titled “Start collecting basic VM performance metrics”

    We are excited to announce that in order to allow STACKIT users to see basic performance metrics of their virtual machines (VMs), we have started installing the OpenTelemetry collector on VMs where the STACKIT Server Agent is running.

    This integration is a significant step towards providing you with deeper, out-of-the-box insights into your infrastructure’s health. The collected metrics data will be visible soon directly within the STACKIT Portal under your server details.

  • announcementruntime

    To align with cloud-native security best practices and further harden your clusters, STACKIT Kubernetes Engine is updating its node configuration.

    Currently, nodes provisioned by STACKIT run the OpenSSH daemon, even though there is no supported method to use it. To reduce the OS-level attack surface and enforce immutable infrastructure practices, the OpenSSH daemon will be permanently disabled on all nodes during scheduled cluster maintenance starting November 5, 2026.

    If you have a specific requirement to keep the OpenSSH daemon active on your nodes, please open a service request via the Help Center. Please note that this is only a temporary exception, and the daemon will eventually be disabled across all clusters.

    Otherwise, no action is required, and your workloads will continue running without interruption.

  • announcementdeveloper-platform

    One SSH address for all STACKIT Git instances

    Section titled “One SSH address for all STACKIT Git instances”

    On October 27, 2026, from 20:00 to 23:00 (UTC), SSH access to STACKIT Git moves to one shared address. The name of your instance becomes the first element of the repository path. This reduces the publicly exposed surface of your instance and lets us improve the reliability of Git operations over SSH in one place.

    • Previous address: git@ssh.<instance>.git.onstackit.cloud:<owner>/<repository>.git
    • Address after the maintenance: ssh://git@ssh.git.onstackit.cloud/<instance>/<owner>/<repository>.git

    During the maintenance every Git instance is restarted once and is unavailable for about one minute. The restarts are staggered, so not all instances are affected at the same time. Access over HTTPS, your repositories, your users, your registered SSH keys and your IP allowlists do not change.

    The previous address keeps working until April 27, 2027. Your existing clones and your automation continue to work after the maintenance, so you can move them at your own pace. We remind you before we switch the previous address off.

    • Allow outbound traffic to 213.17.16.145 on port 22, if your network restricts outbound connections.
    • Add the host key of ssh.git.onstackit.cloud, if your systems verify host keys. Its fingerprint is SHA256:I4jgl6ALgx5qOWwpQVC2M613dV7R0Wy6LfQQ5LQKwR4 (ED25519).
    • Make sure the SSH key your client offers to ssh.git.onstackit.cloud is registered in your instance.
    • Identify every place that holds the address: local clones, build pipelines, deployment automation, infrastructure as code module sources and repository mirrors.

    Update the remote address of each repository:

    Terminal window
    git remote set-url origin "$(git remote get-url origin | sed -E 's#^(ssh://)?git@ssh\.([^.]+)\.git\.onstackit\.cloud[:/]#ssh://git@ssh.git.onstackit.cloud/\2/#')"

    If you have any questions, our Help Center is always at your disposal.