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

fix: check for issuing condition on Certificate #7217

Merged
merged 2 commits into from
Feb 4, 2022

Conversation

backjo
Copy link
Contributor

@backjo backjo commented Sep 15, 2021

When initially creating a cert-manager.io/Certificate object, it shows a degraded status in ArgoCD. To fix this, this PR adds a check for the 'Issuing' condition set to 'true', which means that the certificate is currently being issued and should be treated as 'Progressing', not 'Degraded'

Signed-off-by: Jonah Back jonah@jonahback.com

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

  • 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.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • 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.
  • Optional. My organization is added to USERS.md.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).

Signed-off-by: Jonah Back <jonah@jonahback.com>
@codecov
Copy link

codecov bot commented Sep 15, 2021

Codecov Report

Merging #7217 (3bd1266) into master (f9df915) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #7217   +/-   ##
=======================================
  Coverage   41.91%   41.91%           
=======================================
  Files         177      177           
  Lines       22994    22994           
=======================================
  Hits         9639     9639           
  Misses      11972    11972           
  Partials     1383     1383           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f9df915...3bd1266. Read the comment docs.

@alexmt
Copy link
Collaborator

alexmt commented Sep 29, 2021

Thank you!

@alexmt
Copy link
Collaborator

alexmt commented Oct 1, 2021

The CI is failing due to a broken unit test that is not related to PR. The test is fixed in master already. @backjo can you please merge master changes to pull fix into your fork?

@alexmt alexmt merged commit b6ac9ba into argoproj:master Feb 4, 2022
alexmt added a commit that referenced this pull request Feb 25, 2022
Signed-off-by: Jonah Back <jonah@jonahback.com>

Co-authored-by: Alexander Matyushentsev <AMatyushentsev@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants