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

Add info - When not to use Radix #423

Closed
emirgens opened this issue Nov 27, 2024 · 1 comment · Fixed by #433
Closed

Add info - When not to use Radix #423

emirgens opened this issue Nov 27, 2024 · 1 comment · Fixed by #433
Assignees

Comments

@emirgens
Copy link
Contributor

In the Getting started section, add a new page
When not use Radix
These are not supported in Radix, however some can be done using workarounds

some info....
No direct on-prem connectivity
Need to use own terraform configurations
Need to use own helm charts or flux
Need to use DAPR
Need to use sidecars
Need to have direct access to Kubernetes components (pods, secrets, etc.)
Need low-latency persistant storage (eg. databases and similar)
Needs to accept traffic other than HTTP (eg. mqtt or UDP)
need to run own operators (e.g. redis operator to run Redis database in cluster)

@emirgens
Copy link
Contributor Author

Feedback from DynaGeo team:
https://github.com/equinor/dynageo/issues/4128

@emirgens emirgens linked a pull request Dec 23, 2024 that will close this issue
3 tasks
@emirgens emirgens self-assigned this Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant