We should allow adding, removing, or changing service endpoints on a virtual cluster instance after it has been deployed. This would not involve actually changing what's running inside the container (at least not at first, although automating that would be nice). Instead this is a matter of letting the user update the relevant NodePort/LoadBalancer services to allow access to a service that they have added or changed after deploying the cluster.
First task is to determine how to represent this"service override spec" in the cluster CR. To what extent is it role-level vs member-level.
We should allow adding, removing, or changing service endpoints on a virtual cluster instance after it has been deployed. This would not involve actually changing what's running inside the container (at least not at first, although automating that would be nice). Instead this is a matter of letting the user update the relevant NodePort/LoadBalancer services to allow access to a service that they have added or changed after deploying the cluster.
First task is to determine how to represent this"service override spec" in the cluster CR. To what extent is it role-level vs member-level.