Chapter 6. Known issues


  • SKUPPER-2584 - Multiple Skupper Links

    You can create multiple links from one site to another. However, the links do not perform as expected. For example, traffic flow across multiple links with different costs might not be as expected.

    Workaround

    To workaround this issue, make sure a link does not exist before creating a new link.

  • SKUPPER-2569 - Link cost is not updatable

    If you create a link and later attempt to change the link cost, the update fails.

    Note

    The kubectl get link command reports the updated link cost, however, that link cost does not affect traffic flow.

    Workaround

    To workaround this issue, delete the link and create it again with the desired link cost.

  • SKUPPER-2561 - Orphan connector references

    If you use automation to create a namespace, site and connector resources, you might want to delete the namespace and run your automation again with a new namespace that has the same name. In this scenario, some of the connector resources might still exist and report errors.

    Workaround

    To workaround this issue, consider one of the following:

    • Allow extra time after namespace deletion.
    • Use a random prefix when creating namespace.
  • SKUPPER-869 - Enable idle connection timeouts for the TCP transport

    If an endpoint is terminated, for example a client is killed, the other endpoint observes a half-closed connection. If the other endpoint does not close the connection or attempt to send data to the connection, the Skupper router does not release the memory allocated to that connection

    Workaround

    Avoid client server configurations that use this behavior if possible. For example, if a server automatically closes dormant connections, or attempts to communicate with client, the Skupper router frees the memory when a client is terminated.

Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat