search

grafana / oncall

Developer-friendly incident response with brilliant Slack integration
GNU Affero General Public License v3.0
3.48k stars 285 forks source link

Helm chart - support for kubernetes > 1.25 #4499

Closed cw-sanikachavan closed 1 month ago

cw-sanikachavan commented 4 months ago

What would you like to see!

As per the Readme.md, I can see support until 1.25, by when can we see 1.28+ support for Grafana OnCall?

Product Area

Helm

Anything else to add?

No response

github-actions[bot] commented 4 months ago

The current version of Grafana OnCall, at the time this issue was opened, is v1.6.2. If your issue pertains to an older version of Grafana OnCall, please be sure to list it in the PR description. Thank you :smile:!

EvertonSA commented 4 months ago

i'm already on 1.29 and I have oncall

cw-sanikachavan commented 4 months ago

@EvertonSA yes I got this working by disabling cert-manager and ingress-controller. Have you done the same?

EvertonSA commented 4 months ago

@EvertonSA yes I got this working by disabling cert-manager and ingress-controller. Have you done the same?

indeed, I disable these two and also others like redis and rabbit!

iskhakov commented 1 month ago

As per documentation , we don't recommend running a default configuration that might not support recent versions of k8s. Please disable other components to use oncall in production

Default helm chart configuration is not intended for production. The helm chart includes all the services into a single release, which is not recommended for production usage. It is recommended to run stateful services such as MySQL and RabbitMQ separately from this release or use managed PaaS solutions. It will significantly reduce the overhead of managing them. Here are the instructions on how to set up your own ingress, MySQL, RabbitMQ, Redis