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

Random values regenerating #24658

Closed
gcezaralmeida opened this issue Mar 25, 2024 · 2 comments
Closed

Random values regenerating #24658

gcezaralmeida opened this issue Mar 25, 2024 · 2 comments
Assignees
Labels
harbor solved stale 15 days without activity tech-issues The user has a technical issue about an application

Comments

@gcezaralmeida
Copy link

gcezaralmeida commented Mar 25, 2024

Name and Version

bitnami/harbor 20.1.3

What architecture are you using?

amd64

What steps will reproduce the bug?

  1. I'm using Harbor 20.1.3 Chart from Bitnami with ArgoCD, some secrets keep regenerating and forcing ArgoCD to deploy a new replica set. I saw that this issue was solved in the original Harbor Repo. Is it possible to replicate here?

goharbor/harbor-helm#1612

Are you using any custom parameters or values?

      global:
        imagePullSecrets:
          - docker-registry
      service:
        type: Ingress
      ipFamily:
        ipv6:
          enabled: false
      exposureType: ingress
      nginx:
        replicaCount: 3
      portal:
        replicaCount: 3
      core:
        replicaCount: 3
      jobservice:
        jobLogger: database
        replicaCount: 3
        updateStrategy:
          type: Recreate
      registry:
        replicaCount: 3
      notary:
        replicaCount: 3
      signer:
        replicaCount: 3
      trivy:
        replicaCount: 3
      exporter:
        replicaCount: 3
      ingress:
        core:
          ingressClassName: nginx
          hostname: fortistack-harbor.corp.fortinet.com
          tls: false
          selfSigned: false
          extraTls:
            - hosts:
              - fortistack-harbor.corp.fortinet.com
              secretName: core-harbor-fortinet-tls
      adminPassword: "Harbor12345"
      externalURL: https://fortistack-harbor.corp.fortinet.com
      persistence:
        enabled: true
        imageChartStorage:
          disableredirect: true
          caBundleSecretName: s3-ca
          type: s3
          s3:
            region: us-west-1
            bucket: harbor
            accesskey: admin
            secretkey: 8rt&XuNY414e
            regionendpoint: http://minio.minio.svc:9000
            #encrypt: false
            secure: false
            skipverify: true
            v4auth: true
      postgresql:
        architecture: replication
        readReplicas:
          extendedConfiguration: |
            max_connections = 1024
      redis:
        architecture: replication

What do you see instead?

image

@gcezaralmeida gcezaralmeida added the tech-issues The user has a technical issue about an application label Mar 25, 2024
@github-actions github-actions bot added the triage Triage is needed label Mar 25, 2024
@github-actions github-actions bot removed the triage Triage is needed label Apr 1, 2024
@github-actions github-actions bot assigned aoterolorenzo and unassigned carrodher Apr 1, 2024
Copy link

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Apr 17, 2024
Copy link

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
harbor solved stale 15 days without activity tech-issues The user has a technical issue about an application
Projects
None yet
Development

No branches or pull requests

4 participants