lunny/helm-chart
1
0
Fork 0
Code Issues 36 Pull Requests 14 Actions Packages Projects Releases 93 Wiki Activity

gitea redis cluster for non-HA case #685

New Issue
Closed
opened 2024-07-17 00:42:13 +00:00 by Mohanraj4581 · 1 comment
Mohanraj4581 commented 2024-07-17 00:42:13 +00:00 (Migrated from gitea.com)
Copy Link

Issue Description:
When attempting to use a Redis cluster with Gitea for a non-HA (1 node) scenario with a replica count of 1, the setup is not functioning correctly.

Steps to Reproduce:
Acquired the Gitea HA resources from the repository: Gitea Helm Chart Repo
Modified the replica count to 1 for all resources.
Applied the changes using kubectl apply.

Environment:
Kubernetes environment in bare metal

Detailed Description:
Upon applying the modified configuration, the Gitea pod and Redis cluster pod are stuck in a crash loop. The Gitea logs indicate a failure to connect to the Redis cluster. Although the Redis cluster logs do not show any error, the description reveals a readiness probe failure.

Request:
Please provide guidance on configuring the Redis cluster for a non-HA scenario with Gitea.

Issue Description: When attempting to use a Redis cluster with Gitea for a non-HA (1 node) scenario with a replica count of 1, the setup is not functioning correctly. Steps to Reproduce: Acquired the Gitea HA resources from the repository: Gitea Helm Chart Repo Modified the replica count to 1 for all resources. Applied the changes using kubectl apply. Environment: Kubernetes environment in bare metal Detailed Description: Upon applying the modified configuration, the Gitea pod and Redis cluster pod are stuck in a crash loop. The Gitea logs indicate a failure to connect to the Redis cluster. Although the Redis cluster logs do not show any error, the description reveals a readiness probe failure. Request: Please provide guidance on configuring the Redis cluster for a non-HA scenario with Gitea.
justusbunsi commented 2024-07-17 05:22:24 +00:00 (Migrated from gitea.com)
Copy Link

Redis-HA is not functioning with only one Replica of Redis. Please use Chart version v10.3.0 which provides a non-ha Redis dependency. See https://gitea.com/gitea/helm-chart#single-pod-configurations for example values.

Redis-HA is not functioning with only one Replica of Redis. Please use Chart version [v10.3.0](https://gitea.com/gitea/helm-chart/releases/tag/v10.3.0) which provides a non-ha Redis dependency. See https://gitea.com/gitea/helm-chart#single-pod-configurations for example values.
👍 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
has/backport
in progress
invalid
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/refactor
kind/security
kind/testing
kind/translation
kind/ui
need/backport
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/other
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lunny/helm-chart#685
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?