Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create custom health checks for trident.netapp.io/TridentOrchestrator and trident.netapp.io/TridentBackendConfig #6550

Open
Cajga opened this issue Jun 24, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@Cajga
Copy link
Contributor

Cajga commented Jun 24, 2021

Summary

trident implements a FOSS CSI driver for kubernetes using NetApps appliances as backends. Trident and it's operator using several CRDs to achieve native kubernetes experience.
There are two important CRDs which are interesting with simple installation through ArgoCD:

trident.netapp.io/TridentOrchestrator (used by the trident-operator to install trident itself)

trident.netapp.io/TridentBackendConfig (used by trident to create a TridentBackend based on the configuration defined in this CRD)

We've implemented custom resource health checks for these CRDs and would like to contribute it back to the community.

Motivation

Installing trident with trident-operator using ArgoCD

Proposal

Write the Lua custom resource health checks (we already did and a PR will follow)

@Cajga Cajga added the enhancement New feature or request label Jun 24, 2021
alexmt pushed a commit that referenced this issue Jul 9, 2021
…Orchestrator and trident.netapp.io/TridentBackendConfig (Closes [ISSUE #6550]) (#6552)

* feat: add custom resource health checks for trident.netapp.io/TridentOrchestrator and trident.netapp.io/TridentBackendConfig

Signed-off-by: Balazs Zachar <zachar.balazs@gmail.com>

* feat: extend TridentOrchestrator check with degraded state (based on official documentation)

Signed-off-by: Balazs Zachar <zachar.balazs@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant