argo-cd icon indicating copy to clipboard operation
argo-cd copied to clipboard

feat(health): Implement k8s.mariadb.com CRD health checks

Open sennerholm opened this issue 10 months ago • 0 comments

Health checks for k8s.mariadb.com (https://github.com/mariadb-operator/mariadb-operator) objects, the new name of the mariadb.mmontes.io objects. The main MariaDB healtcheck is also the same.

I doesn't have added "Healthy" testdata and some none-healthy cases, and is asking the users in slack for more samples on "Non Healthy" states that I will add in the future if I get some.

Checklist:

  • [x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • [x] The title of the PR states what changed and the related issues number (used for the release note).
  • [x] The title of the PR conforms to the Toolchain Guide
  • [ ] I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • [ ] I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • [ ] Does this PR require documentation updates?
  • [ ] I've updated documentation as required by this PR.
  • [x] I have signed off all my commits as required by DCO
  • [x] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • [x] My build is green (troubleshooting builds).
  • [x] My new feature complies with the feature status guidelines.
  • [x] I have added a brief description of why this PR is necessary and/or what this PR solves.
  • [ ] Optional. My organization is added to USERS.md.
  • [ ] Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

sennerholm avatar Apr 26 '24 15:04 sennerholm