• Multi-key listeners provide advanced load balancing and failover capabilities with two distribution strategies: priority for ordered failover and weighted for proportional traffic distribution across multiple routing keys. See Creating a multi-key listener using YAML.
• HTTP proxy tunnel support allows Skupper links to traverse corporate HTTP CONNECT proxies, enabling deployment in restricted network environments. See Linking sites through an HTTP proxy.
• Additional Network Observer configuration options provide more flexible observability settings.
• Dynamic system controller for non-Kubernetes sites enables interactive configuration changes on local system sites without requiring service reloads when using --reload-type auto.

CRD changes

• The internal.skupper.io/listener label value on listener Services has changed from true to the name of the listener.

  When Skupper creates a Kubernetes Service for a listener, it sets the label internal.skupper.io/listener on that Service. Previously the value was always true; it is now set to the name of the listener resource.

• The LTS release stream provides only bug fixes. No new enhancements will be added to this stream.
• To remain in a supported configuration, you must upgrade to the latest micro release in the LTS release stream.

• Red Hat OpenShift Container Platform Life Cycle Policy
• Support of Red Hat Middleware products and components on Red Hat OpenShift

Ingress types (primary support)

• LoadBalancer
• OpenShift Routes (supported only on OpenShift)

Kubernetes Ingress types (commercially reasonable support)

• Gateway
• Contour
• Nginx (This requires configuration for TLS passthrough.)
• NodePort

Upgrades

• Red Hat supports upgrades from one downstream minor version to the next, with no jumps.
• While Red Hat aims to have compatibility across minor versions, Red Hat recommends upgrading all sites to the latest version.

• Gathering cluster data - OpenShift sites
• Output of `skupper debug dump' - Kubernetes and local system sites

• Content from redhat.atlassian.net is not included.SKUPPER-3246 - Kube-to-System Site Links Broken: tlsCredentials Secret type Opaque not allowed

  When you upgrade from version 2.1 to version 2.2.1, site links can fail with a TLS credentials secret not found error. This error occurs if you use custom certificates that are stored as an Opaque secret. Version 2.2.1 contains a filter that rejects Opaque secrets and only accepts the kubernetes.io/tls secret type.

  Workaround

  To fix this issue, recreate your custom secret and change its type to kubernetes.io/tls. The system automatically detects the corrected secret and restores the link.

  It is expected that 2.2.2 will accept Opaque secrets again.

• Content from redhat.atlassian.net is not included.SKUPPER-2873 - Collector not reporting traffic correctly

  The collector may not accurately report traffic metrics in certain scenarios.

  Workaround

  To workaround this issue you can restart the deployment with:

  # Replace <your-namespace> with the site namespace.
  kubectl rollout restart deployment skupper-network-observer -n <your-namespace>

  Copy code to clipboard

• Content from redhat.atlassian.net is not included.SKUPPER-2771 - Basic HTTP authentication does not work with NetObs operator

  If you install the Red Hat Service Interconnect Network Observer Operator and create a CR with spec.auth.strategy set to basic, you cannot log into console.

  Workaround

  To workaround this issue you can create a CR with:

  spec:
  ...
    auth:
      strategy: basic
    nginx:
      command:
        - nginx
        - -g
        - daemon off;

  Copy code to clipboard

• Content from redhat.atlassian.net is not included.SKUPPER-2988 - Docker is not supported on IBM Power ppc64le

  Docker is not supported on IBM Power ppc64le.

  Workaround

  To workaround this issue, use Podman instead of Docker.

• Content from redhat.atlassian.net is not included.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.