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

Argo-cd chart not deploy new version redis-ha #2788

Closed
alezander86 opened this issue Jun 21, 2024 · 2 comments
Closed

Argo-cd chart not deploy new version redis-ha #2788

alezander86 opened this issue Jun 21, 2024 · 2 comments
Labels
argo-cd bug Something isn't working no-issue-activity

Comments

@alezander86
Copy link

Describe the bug

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

  1. Try to install argo-helm version 7.2.0

Expected behavior

harbor-ha deployed without errors

Screenshots

image

Additional context

No response

@alezander86 alezander86 added the bug Something isn't working label Jun 21, 2024
@mkilchhofer
Copy link
Member

Hi @alezander86

Can you share some insights of your K8s environment?

  • What k8s version do you use?
  • How many nodes do you have?
  • I see your Pod is pending.
    Can you share the output of kubectl describe pod argo-cd-redis-ha-server-0?

Copy link

github-actions bot commented Sep 9, 2024

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.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
argo-cd bug Something isn't working no-issue-activity
Projects
None yet
Development

No branches or pull requests

3 participants