Lukas May

We are facing the same issue. Given that the issue is quite basic and is open for almost a year and not even the provided examples work: Is the react-native...

We're experiencing the same issue when calling setInputState on the RiveRef. If we wrap the calls in a setTimeout (without a delay) to await pending JS runtime executions it works....

We're also seeing issues with the "routing-serving-certs" issuance: `Failed to wait for order resource "routing-serving-certs-1-422265175" to become ready: order is in "errored" state: Failed to create Order: 400 urn:ietf:params:acme:error:rejectedIdentifier: Error...

Same here. For us it's concerning that when creating a cluster, we're limited to 2Gbps of bandwidth

We could solve this issue by increasing the memory limits & requests

We're seeing the same problem with Chat messages not being shown directly after joining the room. It takes sometimes like 30 min for them to be visible in the UI

Knative Serving Resource - we have tried uninstalling it and re-installing it from scratch and have increased the memory as we saw some OOMKilled errors. ``` apiVersion: operator.knative.dev/v1beta1 kind: KnativeServing...

I now even tried to remote knative entirely and also delete all resources related to it by deleting all resources with knative in the type. The error still persists >...