This repository has been archived by the owner on Jun 28, 2022. It is now read-only.
Update CRD versions #44
Labels
area/dependency
Issues or PRs related to dependency changes.
area/httpproxy
Issues or PRs related to the HTTPProxy API.
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
lifecycle/accepted
Denotes an issue that has been triaged and determined to be valid.
Comments
|
Doing this should fix #41 as well. |
youngnick
added
area/dependency
youngnick
pushed a commit
to youngnick/ir2proxy
that referenced
this issue
Jun 1, 2020
Fixes projectcontour#44 Fixes projectcontour#41 This commit updates the Contour dependency to v1.5.0, meaning that objects that are generated no longer require a `status: {}` stanza in them to pass CRD validation. However, this means that this commit also requires that Contour v1.5.0 be running in any clusters you are converting. Signed-off-by: Nick Young <[email protected]>
Update in what way? |
|
Just update the dependency from v1.1.0 to v1.4.0 (I think?) whichever version was the last we had ingressroute support. I made some changes to the HTTPProxy spec that make the objects a little tidier. |
|
is this still on your radar? @youngnick |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We should update the HTTPProxy CRD spec, it will mean that no empty
status: {}fields are output, now that there is a status subresource.The text was updated successfully, but these errors were encountered: