Skip to content

Conversation

@sanposhiho
Copy link
Member

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #355

Does this PR introduce a user-facing change?:

NONE

@sanposhiho
Copy link
Member Author

I couldn't imagine a case where a cronjob is not healthy, so I made it to always return KubernetesResourceState_HEALTHY.

@pipecd-bot
Copy link
Collaborator

COVERAGE

Code coverage for golang is 33.80%. This pull request decreases coverage by -0.00%.

File Function Base Head Diff
pkg/app/piped/cloudprovider/kubernetes/state.go determineCronJobHealth 0.00% 0.00% +0.00%

@sanposhiho sanposhiho marked this pull request as ready for review January 11, 2021 13:11
@nakabonne
Copy link
Member

Yep, we finely watch the Job's health. So I feel like it's enough to give back "HEALTHY" as well. Thanks 👍
/lgtm

@nghialv
Copy link
Member

nghialv commented Jan 12, 2021

/approve

@pipecd-bot
Copy link
Collaborator

APPROVE

This pull request is APPROVED by nghialv.

Approvers can cancel the approval by writing /approve cancel in a comment. Any additional commits also will change this pull request to be not-approved.

@pipecd-bot pipecd-bot merged commit 2766217 into master Jan 12, 2021
@pipecd-bot pipecd-bot deleted the health-state-cronjob branch January 12, 2021 02:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Check health state of CronJob resource

5 participants