-
Notifications
You must be signed in to change notification settings - Fork 690
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
internal: Update DAG status updates to go via k8s/StatusUpdateHandler #2560
Labels
area/status
Issues or PRs related to exposing status for APIs.
blocked
Blocked waiting on a dependency
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.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Comments
3 tasks
Blocked on #2572. |
youngnick
pushed a commit
to youngnick/contour
that referenced
this issue
Jun 19, 2020
Updates the DAG StatusClient to use the StatusUpdateWriter pattern. Fixes projectcontour#2560 Fixes projectcontour#2580 Fixes projectcontour#2522 We should be able to remove the StatusClient eventually, but that API also needs refactoring for adding Conditions (currently under projectcontour#2495), so for now I've just updated it to send updates via the StatusUpdateWriter rather than make API calls directly. Signed-off-by: Nick Young <[email protected]>
youngnick
pushed a commit
to youngnick/contour
that referenced
this issue
Jun 19, 2020
Updates the DAG StatusClient to use the StatusUpdateWriter pattern. Fixes projectcontour#2560 Fixes projectcontour#2580 Fixes projectcontour#2522 We should be able to remove the StatusClient eventually, but that API also needs refactoring for adding Conditions (currently under projectcontour#2495), so for now I've just updated it to send updates via the StatusUpdateWriter rather than make API calls directly. Signed-off-by: Nick Young <[email protected]>
youngnick
pushed a commit
to youngnick/contour
that referenced
this issue
Jun 19, 2020
Updates the DAG StatusClient to use the StatusUpdateWriter pattern. Fixes projectcontour#2560 Fixes projectcontour#2580 Fixes projectcontour#2522 We should be able to remove the StatusClient eventually, but that API also needs refactoring for adding Conditions (currently under projectcontour#2495), so for now I've just updated it to send updates via the StatusUpdateWriter rather than make API calls directly. Signed-off-by: Nick Young <[email protected]>
youngnick
pushed a commit
to youngnick/contour
that referenced
this issue
Jun 19, 2020
Updates the DAG StatusClient to use the StatusUpdateWriter pattern. Fixes projectcontour#2560 Fixes projectcontour#2580 Fixes projectcontour#2522 We should be able to remove the StatusClient eventually, but that API also needs refactoring for adding Conditions (currently under projectcontour#2495), so for now I've just updated it to send updates via the StatusUpdateWriter rather than make API calls directly. Signed-off-by: Nick Young <[email protected]>
youngnick
pushed a commit
to youngnick/contour
that referenced
this issue
Jun 19, 2020
Updates the DAG StatusClient to use the StatusUpdateWriter pattern. Fixes projectcontour#2560 Fixes projectcontour#2580 Fixes projectcontour#2522 We should be able to remove the StatusClient eventually, but that API also needs refactoring for adding Conditions (currently under projectcontour#2495), so for now I've just updated it to send updates via the StatusUpdateWriter rather than make API calls directly. Signed-off-by: Nick Young <[email protected]>
youngnick
pushed a commit
to youngnick/contour
that referenced
this issue
Jun 19, 2020
Updates the DAG StatusClient to use the StatusUpdateWriter pattern. Fixes projectcontour#2560 Fixes projectcontour#2580 Fixes projectcontour#2522 We should be able to remove the StatusClient eventually, but that API also needs refactoring for adding Conditions (currently under projectcontour#2495), so for now I've just updated it to send updates via the StatusUpdateWriter rather than make API calls directly. Signed-off-by: Nick Young <[email protected]>
youngnick
pushed a commit
that referenced
this issue
Jun 19, 2020
Updates the DAG StatusClient to use the StatusUpdateWriter pattern. Fixes #2560 Fixes #2580 Fixes #2522 We should be able to remove the StatusClient eventually, but that API also needs refactoring for adding Conditions (currently under #2495), so for now I've just updated it to send updates via the StatusUpdateWriter rather than make API calls directly. Signed-off-by: Nick Young <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/status
Issues or PRs related to exposing status for APIs.
blocked
Blocked waiting on a dependency
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.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Move the existing DAG rebuild status updates to use StatusUpdateHandler, including adding support for IngressRoute and HTTPProxy valid and desc fields. This may involve a small update to IngressRoute to enable the status subresource, so that the same code paths can be used for everything.
Work initially part of #2371, but pulled out because it's bigger than I thought.
The text was updated successfully, but these errors were encountered: