Ted Ross

On Wed, May 19, 2021 at 5:21 PM RajKuni ***@***.***> wrote: > Hi, > > I've been using Skupper in a dev environment to connect services in > multiple clusters....

RajKuni, Would you be willing to share a little bit about your use case? What is it you wish to accomplish with a Helm chart? What is the scale and...

It's more likely that the environment is probing the open ports for some reason. There are connection attempts at both the interior and edge listening ports. Those can probably be...

For the record, that backtrace is from the prototype collector (nodejs). Can you run `skupper version` in that environment to see what images are being used?

For your convenience... Here is the cleanup script to un-do the above reproducer: ```bash NS_PREFIX=demo for i in dmz-a dmz-b; do kubectl delete accessgrant $i-grant -n ${NS_PREFIX}-$i kubectl delete routeraccess...

Possible root cause: The router has a new behavior post-3.0.0 (I was running the latest in this test). SslProfiles now load the referenced certificate files immediately upon configuration. The old...

skstat -c output: ``` Connections id host container role proto dir security authentication meshId last dlv uptime ================================================================================================================================================================== 1 ::1:56300 kube-flow-collector normal amqp in no-security no-auth 000:00:00:01 000:01:46:38 2 ::1:56316...

As I understand it, there is no reason that we can't produce arm64 images for Skupper. The skupper-router code is known to build on aarch64. -Ted On Mon, Sep 19,...

When you ran `skupper init`, did you supply the `--enable-cluster-permissions` option? ``` $ skupper-1.7.0 init --help | grep cluster-permissions --enable-cluster-permissions Enable cluster wide permissions in order to expose deployments/statefulsets in...