Chapter 7. Known issues

SKUPPER-1802 - skupper service status reports a service that doesn’t exist on the current site

If you disabled service-sync on your network and expose a service on one site, the skupper service status command reports those services as existing on all other sites even though that service does not exist on thoses sites.

Workaround

To workaround this issue use skupper service status -v to understand exposed services and availability.

For example, on the west site:

$ skupper service status

Services exposed through Skupper:
╰─ backend:8080 (tcp)

However, that service does not exist on the west site. Use the verbose output to show that the service only exists on the east site:

$ skupper service status -v

Services exposed through Skupper:
╰─ backend:8080 (tcp)
   ╰─ Sites:
      ╰─ 316fbe31-299b-490b-9391-7b46507d76f1(east)
         │ policy: disabled
         ╰─ Targets:
            ╰─ backend:8080 name=backend-9d84544df-rbzj

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.

SKUPPER-805 - skupper init doesn’t work for ordinary user on OCP 3.11

Workaround

Two workarounds are available:

---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: skupper-non-admin
rules:
- apiGroups:
  - ""
  resources:
  - configmaps
  - pods
  - pods/exec
  - services
  - secrets
  - serviceaccounts
  verbs:
  - get
  - list
  - watch
  - create
  - update
  - delete
- apiGroups:
  - apps
  resources:
  - deployments
  - statefulsets
  - daemonsets
  verbs:
  - get
  - list
  - watch
  - create
  - update
  - delete
- apiGroups:
  - route.openshift.io
  resources:
  - routes
  verbs:
  - get
  - list
  - watch
  - create
  - delete
- apiGroups:
  - networking.k8s.io
  resources:
  - ingresses
  - networkpolicies
  verbs:
  - get
  - list
  - watch
  - create
  - delete
- apiGroups:
  - projectcontour.io
  resources:
  - httpproxies
  verbs:
  - get
  - list
  - watch
  - create
  - delete
- apiGroups:
  - rbac.authorization.k8s.io
  resources:
  - rolebindings
  - roles
  verbs:
  - get
  - list
  - watch
  - create
  - delete

You can save the YAML above to role.yaml, apply it and bind the role to a username using:

$ oc apply -f role.yaml
$  oc policy add-role-to-user skupper-non-admin <username> -n <namespace-name> --role-namespace=<namespace-name>