You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when I am trying to deploy a new argo-helm with Redis-ha
Initializing config..
Copying default redis config..
to '/data/conf/redis.conf'
Copying default sentinel config..
to '/data/conf/sentinel.conf'
Identifying redis master (get-master-addr-by-name)..
using sentinel (argo-cd-redis-ha), sentinel group name (argocd)
Could not connect to Redis at argo-cd-redis-ha:26379: Try again
Could not connect to Redis at argo-cd-redis-ha:26379: Try again
Could not connect to Redis at argo-cd-redis-ha:26379: Try again
Fri Jun 21 16:11:46 UTC 2024 Did not find redis master ()
Identify announce ip for this pod..
using (argo-cd-redis-ha-announce-0) or (argo-cd-redis-ha-server-0)
identified announce ()
/readonly-config/init.sh: line 239: Error: Could not resolve the announce ip for this pod.: not found
here are my values
argo-cd:
redis-ha:
enabled: true
redis:
enabled: false
server:
replicas: 1
env:
- name: ARGOCD_API_SERVER_REPLICAS
value: '1'
controller:
enableStatefulSet: true
dex:
enabled: false
# Disabled for multitenancy env with single instance deployment
applicationSet:
enabled: true
# Disable for now, since we don't have any notifications
notifications:
enabled: false
params:
server.insecure: true
application.namespaces: >-
env1
applicationsetcontroller.namespaces: >-
env1
applicationsetcontroller.allowed.scm.providers: "https://git.example.com/,https://gitlab.example.com/"
applicationsetcontroller.enable.scm.providers: "false"
Related helm chart
argo-cd
Helm chart version
7.2.0
To Reproduce
Try to install argo-helm version 7.2.0
Expected behavior
harbor-ha deployed without errors
Screenshots
Additional context
No response
The text was updated successfully, but these errors were encountered:
This issue 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.
Describe the bug
when I am trying to deploy a new argo-helm with Redis-ha
here are my values
Related helm chart
argo-cd
Helm chart version
7.2.0
To Reproduce
Expected behavior
harbor-ha deployed without errors
Screenshots
Additional context
No response
The text was updated successfully, but these errors were encountered: