Integration with Skupper

[rigazilla]

Skupper (https://skupper.io/) is a k8s component that provides intercluster communication. Investigate if it can be useful to semplify cross site replication configuration.

[dmvolod]

I guess we can't utilize Skupper now, as it lack a large number of configuration possibilities required for the automatic operator management (not for end users)

• no fully functional operator (just install skupper-site-controller via OLM)
• no operator on the operatorhub.io published
• no CRD for configuration (configuration via ConfigMap only, not possible to validate that's skupper installed or not via CRD)
• service expose via cli (skupper) only. All cmd logic need to be re-implemented inside operator for automation
• Skupper connects on the namespace level, but Infinispan CR is on the individual cluster operation, that's missing automation setup steps
• if Skupper token leaked, anyone will get access to the cluster services operated by Skupper

I think it's better to combine solution described #1033 and GossipRouter deployment

[pruivo]

there is another tool on the table: https://submariner.io/

[dmvolod]

I think we can try to utilize both solutions, but first step install and configure Skupper or Submariner will be so huge However next steps will be more easy

[pruivo]

at least, the submariner has an operator: https://operatorhub.io/operator/submariner

not sure how good it is neither what it does xD

[dmvolod]

not sure how good it is neither what it does xD

Yeah, it utilize sigs.k8s.io/mcs-api and easy to expose cross-site services

[dmvolod]

But seems to need access to the remote cluster Kubernetes API. In this case there is no value, except granting access on the k8s cluster level, not individual Infinispan https://submariner.io/getting-started/architecture/