Maybe start with bitnamisecure repo directly.
Example: #368

We could also merge both PRs and make it the zammad 7.0 updater PR.
Thoughts?

Maybe start with bitnamisecure repo directly. Example: #368

We could also merge both PRs and make it the zammad 7.0 updater PR. Thoughts?

@monotek I'm not sure what the best way is. We could have one branch with all changes for Zammad 7.0 (#348), where we merge other MRs like this one as squash merges. We'd have to change to the develop tag in this branch, and then finally on merging set it back to a normal 7.0 value. This might lead to a MR with several files changed.

Alternative would be to keep multiple MRs like this one around, and merge them one after the other after Zammad 7.0 is available, resulting in multiple new chart versions.

@klml here are the changes for Redis Sentinel support. The Zammad image for develop has it already, so if you use this branch with the develop image, you can create a test deployment with Redis Sentinel. Could you do that and provide us with your feedback on it, please?

This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.