Fernando Giorgetti

Hello Alba, You're exposing a service, but if your intention is to have access to each pod by name directly, I would recommend you adding the "--headless" flag to the...

Since you're deploying the same statefulset and service on both namespaces, could you try to modify their names in one of the clusters, possibly just changing the suffix in one...

Hello Alba, Looking at your statefulset, I noticed it has the following specification: ordinals: start: 2 Do you really need to set the start index for your worker pods? If...

Some clusters might have securitycontextconstraints preventing pods from running as root, therefore they won't be able to bind system ports ( wrote: > Further debugging, even though I executed the...

One comment to add here is that the `--output` flag is currently working for system sites.

One thing to consider here, would be to use the Listener.metadata.labels and annotations, instead of introducing new fields to the CRD, which would imply a new version. If passing the...

@dhia-gharsallaoui there is a possible issue with this approach for propagating annotations, as more complex data could be passed, like json (that could break the value parsing). But we could...

When the service does not exist, the controller is currently adding: ```yaml annotations: internal.skupper.io/controlled: "true" ``` I agree. It should not touch a service that is not controlled.

@nluaces @pwright I like the idea of having this being generated automatically, maybe on each PR merged or as a scheduled workflow in the CI. Can we get these markdown...

More appropriate names could be: * `system-setup.sh` and `system-teardown.sh`