Skip to content
This repository has been archived by the owner on Aug 12, 2024. It is now read-only.

CRD Validator Follow-up #244

Closed
tylerslaton opened this issue Apr 14, 2022 · 0 comments
Closed

CRD Validator Follow-up #244

tylerslaton opened this issue Apr 14, 2022 · 0 comments
Assignees
@tylerslaton
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
backlog

Comments

@tylerslaton
Copy link
Contributor

tylerslaton commented Apr 14, 2022 •
edited
Loading

The crdvalidator work has landed but there are a few lingering issue we should tidy up before moving on from it.

  1. Add working rejection cases to the e2e suite. Handled in PR.
  2. (tylerslaton): Check CRDValidator safe storage logic #243
  3. Create an "install-webhooks" make target to prevent installing cert-mgr twice. Handled in PR.
  4. Add unit tests to the crd package. Handled in PR.
  5. Potentially remove the attached shell from the Dockerfile (:debug tag on the image) Handled in separate issue.
@tylerslaton tylerslaton self-assigned this Apr 14, 2022
@timflannagan timflannagan added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Apr 20, 2022
@timflannagan timflannagan added this to the backlog milestone Apr 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@tylerslaton tylerslaton

Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
backlog
Development

No branches or pull requests
2 participants
@timflannagan @tylerslaton