Zum Inhalt springen
Produkte
Plattform
Developer Tools
Portal

FAQ

Diese Seite ist noch nicht in deiner Sprache verfügbar. Englische Seite aufrufen

  • Tooling

    Can I use the STACKIT CLI to manage STACKIT Edge Cloud?

    Yes! In the latest release of the STACKIT CLI you’ll find a subset of edge commands to manage your STACKIT Edge Cloud products.

    Can I use the STACKIT Terraform Provider to manage STACKIT Edge Cloud?

    Yes! In the latest release of the STACKIT Terraform Provider you’ll find resources to manage your STACKIT Edge Cloud products.

  • General

    Can I run AI/LLM workloads on my GPU-servers when using STACKIT Edge Cloud?

    Yes! You’ll need to select the appropriate extensions when creating your STACKIT Edge Cloud image. Please follow the advanced topic about using extensions for more information.

    My hosts are running behind a proxy, can I still use STACKIT Edge Cloud?

    Yes, you can! There are different options to configure different proxy settings and you’ll find examples how to do it in the respective sections of the user guide:

    • Proxy settings to use when booting from a STACKIT Edge Cloud image: boot customization
    • Proxy settings to use after creating a Kubernetes cluster: config patches
    • STACKIT Edge Cloud proxy feature, when facing network restrictions trying to manage your cluster: cloud proxy

    Which responsibility do I have when using the service and what's provided by STACKIT?

    Please refer to the shared responsibility model to learn more about the responsibilities of STACKIT and the customer when using STACKIT Edge Cloud.

    What are the requirements when using STACKIT Edge Cloud?

    This is a partial list of requirements to use STACKIT Edge Cloud:

    • Every edge host needs be able to establish a outgoing network connection to stackit.cloud via TCP port 443.
    • Talos Linux requires internet access to download the Talos installer and container images, as described in the Talos documentation.
      • As a minimum access to the following public repositories is require:
        • gcr.io (Google Container Registry)
        • ghcr.io (GitHub Container Registry)
        • registry.k8s.io (Kubernetes Container Registry)
      • The registries may change depending on the Talos version used. A recent list of registries required can be found by running the command talosctl images default of the matching talosctl version
      • If you operate a internal registry mirror you may configure this mirror to be used instead. This can be configured either post-boot using the machine configuration or pre-boot using the talos.config Kernel parameter. Please review the boot customization and config patches documentation for details how to perform such customizations.

    What are the current limitations of STACKIT Edge Cloud?

    This is a partial list of limitations when using STACKIT Edge Cloud:

    • STACKIT Edge Cloud is sized and tested for up to 1000 accumulated EdgeCluster objects per instance. If you chose to manage more objects than this you may run into a unsupported state.
    • Currently there are no guarantees that a specific single board computer (SBC) supported by Talos is also compatible with STACKIT Edge Cloud.
    • Please take a look at the STACKIT service certificate for Edge Cloud to get a better understanding of the current product SLA.

    Something isn't working. Where do I get help?

    Please take a look at our troubleshooting guide. We try to cover the most common issues and how to fix them there. If you can’t find the right solution for your problem there feel free to contact the STACKIT support.

  • Common issues

    Talos is stuck in the booting stage. What to do?

    There are many possible reasons why Talos Linux may get stuck in the booting stage. We’ll discuss the most common ones here:

    Disk size to small

    Section titled “Disk size to small”

    Symptoms

    Section titled “Symptoms”

    The list of symptoms is not complete and symptoms non-exclusive. In your Talos console you see logs such as:

    • ERROR source=EdgeHostlet msg="Reconciler error" err="rpc error: code = FailedPrecondition desc = bootstrap is not available yet"
    • volume status {"component": "controller-runtime", "controller": "block.VolumeManagerController", "volume": "EPHEMERAL", "phase": "failed -> failed", "error": "no disks matched for volume"}

    Causes

    Section titled “Causes”

    Possible causes include, but are not limited to:

    • The installation disk is to small in capacity.
      • Solution: make sure you use a medium with at least 32GiB of capacity, see Talos system-requirements. 100GiB are recommended by STACKIT.
    • You are using a raw image and haven’t resized it
      • Solution: make sure you resize your raw image so it’s at least 32GiB of capacity, see Talos system-requirements. 100GiB are recommended by STACKIT.