Feature: Add ArgoCD widget

[fcornelius]

Proposed change

This adds a widget for ArgoCD. It can list the count of apps present in an ArgoCD instance by app status, e.g. synced or healthy.

Closes #2644

Type of change

• New service widget
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation only
• Other (please explain)

Checklist:

• If applicable, I have added corresponding documentation changes.
• If applicable, I have reviewed the feature and / or service widget guidelines.
• I have checked that all code style checks pass using pre-commit hooks and linting checks.
• If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.

[shamoon]

The length of the docs here backs up my theory that k8s is too complicated. If you’d think there’s a way to make it more concise (mostly linking to other places ) that’d be great, I didn’t see anything obvious.

As for the widget, if you wouldn’t mind copy pasting some sample api output for me to test.

Finally, one thing is all widgets should display no more than 4 blocks. I’ll have a real look once you have a chance to supply the above.

thanks

[fcornelius]

I feel you, the doc however is not related to kubernetes itself. It's due to the way roles are configured in ArgoCD, which is a little unintuitive and I wanted to include a security best practice rather than just the quickest solution to get it running.

Limited the maximum fields shown to 4 now.

Sample API response to test with: <removed>
This one should yield the fields:
apps: 4, synced: 2, outOfSync: 2, healthy: 1, missing: 1, degraded: 1, progressing: 1

[shamoon]

Thanks, seems to work well just some small things.

[shamoon]

Awesome thanks

[fcornelius]

Awesome thanks

Thank you for this cool project!

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.