AutoScalingListener is created but remains OutOfSync

[hhami-newday]

Hello! I am fairly new to ArgoCD and k8s so maybe it is a silly question.

I have created a multi-source application in ArgoCD which builds the controller and the scale-set. In Github, I can queue a workflow using the correct runs-on label and it all works as expected.

However in ArgoCD, the controller (I am assuming) creates an autoscalinglistener (and a role / rolebinding resource) at the top-level of the application.

This means that my ArgoCD sync always shows as OutOfSync as the desired manifest is blank but live manifest is obviously populated. Have I done something wrong here?

Side note: The listener pod running under the autoscalinglistener never reaches healthy state. It is always 'progressing' but the app itself seems to work and run my actions accordingly.

Any guidance is appreciated!

[luis-lf]

I have the same issue, everything seems to work fine but argo shows that the scale-set app is out of sync with this message for the listener role and role-binding:

 OutOfSync (This resource is not present in the application's source. It will be deleted from Kubernetes if the prune option is enabled during sync.)

Were you able to find a solution for this?

[hhami-newday]

I wasn't. I was hoping someone could shed some light on it.

You can do some resource exclusions in ArgoCD but currently my implementation shares a namespace with some other applications and I think the exclusions cannot be granular enough for me to exclude just these particular components for this application. I believe it would affect other kinds (roles, for example) in the same namespace which isn't what I want.

If you have it in a completely isolated namespace, maybe that will work for you.

[juris]

Same here. scale-set-controller:0.9.3 ArgoCD:2.12.0

[AurimasNav]

I wasn't. I was hoping someone could shed some light on it.

You can do some resource exclusions in ArgoCD but currently my implementation shares a namespace with some other applications and I think the exclusions cannot be granular enough for me to exclude just these particular components for this application. I believe it would affect other kinds (roles, for example) in the same namespace which isn't what I want.

If you have it in a completely isolated namespace, maybe that will work for you.

It does not seem to have namespace parameter so it is cluster wide.

[SPodjasek]

See this comment: #3533 (comment)

[juris]

Found the related issue

[SPodjasek]

And this comment should be referenced as an resolution:

#3533 (comment)