Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose Stargate env vars in K8SandraCluster #1340

Closed
jahstreet opened this issue Jun 4, 2024 · 1 comment
Closed

Expose Stargate env vars in K8SandraCluster #1340

jahstreet opened this issue Jun 4, 2024 · 1 comment
Labels
done Issues in the state 'done' enhancement New feature or request

Comments

@jahstreet
Copy link

jahstreet commented Jun 4, 2024

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?:

@jahstreet jahstreet added the enhancement New feature or request label Jun 4, 2024
@jahstreet
Copy link
Author

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.

@adejanovski adejanovski added the done Issues in the state 'done' label Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
done Issues in the state 'done' enhancement New feature or request
Projects
Status: Done
Development

No branches or pull requests

2 participants