You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stargate cannot be customized with env vars when is deployed with K8SandraCluster CRD. Env vars are used by the Stargate entrypoint - starctl script.
Why do we need it?
There is not way to configure proxy protocol (and do other starctl customizations) for Stargate, which is required for running it on K8s behind LB to be exposed outside of K8s. Alternative is to deploy it separately from K8SsandraCluster, but ofc it is just a workaround.
Environment
K8ssandra Operator version:
latest (1.16.0 as of today)
Anything else we need to know?:
The text was updated successfully, but these errors were encountered:
We explored the topic better, apparently proxy mode is meant to be used for the different things, however, the env vars are still not exposed by the operator. So for us it becomes irrelevant, but for teams relying on more customizations, it will still be the case.
What is missing?
Stargate cannot be customized with env vars when is deployed with K8SandraCluster CRD. Env vars are used by the Stargate entrypoint - starctl script.
Why do we need it?
There is not way to configure proxy protocol (and do other starctl customizations) for Stargate, which is required for running it on K8s behind LB to be exposed outside of K8s. Alternative is to deploy it separately from K8SsandraCluster, but ofc it is just a workaround.
Environment
K8ssandra Operator version:
latest (1.16.0 as of today)
Anything else we need to know?:
The text was updated successfully, but these errors were encountered: