The ApplicationSet controller manages multiple Argo CD Applications as a single ApplicationSet unit, supporting deployments to large numbers of clusters, deployments of large monorepos, and enabling secure Application self-service.
I have the following ApplicationSet that worked at some point. But I have no idea what I changed in order to it to stop working (creates no Application when the patterned branch is pushed):
If I set no github secret I get from the applicationset-controller pod:
time="2023-05-08T22:11:08Z" level=error msg="error generating application from params" error="error listing repos: error listing repositories for xxxxxx: GET https://api.github.com/orgs/xxxxx/repos?per_page=100: 403 API rate limit exceeded for x.x.x.x. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.) [rate reset in 59m54s]" generator="{<nil> <nil> <nil> 0xc001003520 <nil> <nil> <nil> <nil>}"
As I mentioned, it worked when I was using my feature branch for the whole cluster. This is the only meaningful thing I changed as far as I can remember.
The applicationset is indeed created, but no application below it.
I wonder why I get no output at all when using a good (full access) API Token (personal).
I have the following
ApplicationSet
that worked at some point. But I have no idea what I changed in order to it to stop working (creates noApplication
when the patterned branch is pushed):If I set no github secret I get from the applicationset-controller pod:
If I do set the secret I get only:
As I mentioned, it worked when I was using my feature branch for the whole cluster. This is the only meaningful thing I changed as far as I can remember.
The applicationset is indeed created, but no application below it. I wonder why I get no output at all when using a good (full access) API Token (personal).
dex: 2.30.2 argocd: 2.4.11
Any directions?