Chapter 8. Known issues

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.

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>

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;

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.

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.