After upgrade to 1.15.0 - 1.16.0 Agocd no longer sync's with git repos

Bug

Argocd can't sync with repos after update in tag: "3.6.8-bb.6"

Description

After upgrade to BB 1.15.0 - 1.16.0, Agocd no longer sync's with git repos. When I override Argocd to use #tag: "3.6.8-bb.5" Argocd works as expected. As far as I can see it has to do with the redis update.

BigBang Version

BB 1.14.1

@jason.crothers we added resource limits and requests to redis. Are you seeing the redis pods restarting? You can increase the redis resources by passing in the following at the bigbang level:

addons:
  argocd:
    enabled: true
    values:
      redis-bb:
        master:
          resources:
            requests:
              memory: 64Mi
              cpu: 50m
            limits:
              memory: 64Mi
              cpu: 50m
        replica:
          resources:
            requests:
              memory: 64Mi
              cpu: 50m
            limits:
              memory: 64Mi
              cpu: 50m

The values above are what they are set to by default.

I will put in an MR increase the resources

changed milestone to %1.17.0

changed iteration to Big Bang Iterations Sep 7, 2021 - Sep 20, 2021

set weight to 1

added argocd priority4 statusreview labels

assigned to @BrandenCobb

mentioned in merge request !903 (merged)

I didn't see a problem with redis servers and resources. However, repo and controller did need some modifications. I will remove my tag overlay and try out new argocd again to double check redis resources. Here is what I needed to bump those other resources up to.

     repoServer:
        resources:
         limits:
           cpu: 100m
           memory: 1Gi
         requests:
           cpu: 50m
           memory: 0.5Gi
      controller:
        resources:
         limits:
           cpu: 500m
           memory: 3Gi
         requests:
           cpu: 100m
           memory: 2Gi

I will add those to my MR. Thank you we need more real-world resource data to help set these values.

Ok, I guess after making the resource changes I mentioned. I just had to go and do a Hard-Refresh on just about everything. The Redis defaults for resources are good, didn't have to change those. I guess we can close this out.

We have seen some other issues with the redis resources, so I went ahead and upped them anyways. This will get closed when the linked MR is merged into BB.

closed with merge request !903 (merged)

mentioned in commit fb43e019

removed statusreview label