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

[Feature]: redis #62

Open
diwakrchitoor opened this issue Sep 23, 2024 · 2 comments
Open

[Feature]: redis #62

diwakrchitoor opened this issue Sep 23, 2024 · 2 comments
Assignees
Labels
feature New feature or request triage Needs to be triaged

Comments

@diwakrchitoor
Copy link

Affected Chart

icinga-stack

Please describe your feature request

No response

@diwakrchitoor diwakrchitoor added feature New feature or request triage Needs to be triaged labels Sep 23, 2024
@diwakrchitoor
Copy link
Author

Hi, Please add place for configuring redis in Icinga kubernetes chart

@srvrguy
Copy link

srvrguy commented Dec 2, 2024

What part of Redis do you need configured? Are you talking about configuring for an external server, or the in-chart deployment?

My opinion is that the in-chart Redis and MySQL pods are really only suited for testing purposes. For production deployments, it is better to use an independent install. You can do this either via a separate k8s install of the services or using a cloud-managed version, if you're using a cloud provider with that option. This gives you a lot of flexibility on how the service is deployed, configured, and managed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request triage Needs to be triaged
Projects
None yet
Development

No branches or pull requests

3 participants