k8ssandra
K8SSAND-1785 ⁃ Update K8ssandra operator to deploy Stargate v2
Stargate v2 Beta 1 is now available, so suggest we start thinking about how to update K8ssandra operator to run Stargate v2.
In the v2 architecture, the following API services are now independently deployable and should be run in their own pods / scaled via K8s Deployments: REST, GraphQL, Docs API. Configurable options for each API service should include number of instances (default to 0?), container image, and possibly affinity. Options for deploying the coordinator node should remain as in Stargate v1.
The docs should also be updated to reflect the SGv2 architecture. for example, the Stargate component page.
┆Issue is synchronized with this Jira Story by Unito
Given that the stargate_4.0 image is EOL, is there any timeline for this work or estimates on how much effort will be involved in moving to v2 image(s)?
I'm now hearing rumors that the Stargate project itself is EOL - can anyone confirm this?
@ericsmalling Not my bread, but I really doubt Stargate will be EOLed, it's seems to be pretty active in development.
https://github.com/stargate/stargate/pulse
@adejanovski Do you know if this feature request is going to get picked up?
Stargate V2 is the main focus of the Stargate team, but AFAIK the only way to deploy Stargate on K8s (OpenShift) is via K8ssandra-operator.
