Abiliy to define "external" servers

[ajh123]

I have a couple Fabric servers that I would like to add to all my Shulker proxies.
These Fabric servers are not managed by Kubernetes so they would be classed as "external".

This would require two features:

• predefine the proxy's forwarding secret (so it is known before proxy is made and it can be manually set on the external server)
• define a list of external servers (see example YAML)

apiVersion: shulkermc.io/v1alpha1
kind: ProxyFleet
metadata:
  name: public
spec:
  clusterRef:
    name: getting-started
  replicas: 1
  service:
    type: LoadBalancer
    externalTrafficPolicy: Local
  template:
    spec:
      version:
        channel: Velocity
        name: latest
      externalServers:
        - Creative: # <- this would be the name of the server
          address: 1.1.1.1:25565
        - Survival:
          address: 1.1.1.1:25566

Currently I would like to migrate my current set up to Shulker which uses Paper for lobbies, a "bear metal" Velocity
, and two Fabric servers. Since I don't need full scalability for these Fabric servers I would like to stick to running these "bear metal" (and Shulker does not support Fabric anyway).

[jeremylvln]

Hi @ajh123

That's a fantastic idea, I would add these to the MinecraftCluster resource so all proxies have access to this list. I would need some modification of the proxy agent because it's only watching events in the Kubernetes cluster, so it would need to have access to this list too. Give me some time to think about it, but I love this idea.

Thanks!

[jeremylvln]

This feature is now part of the 0.10.0 release.

It still lacks of documentation, but I plan a big overhaul to fix all the issues listed in #435. Until then, look at the PR adding the feature for an example.

[ajh123]

Thanks, for the release. I've already tried out the feature and it works perfectly.