-
Notifications
You must be signed in to change notification settings - Fork 1
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
Adds a HTTP controller implementation #17
Conversation
Controllers interfacing over HTTP will not be checking in or publishing liveness updates
The HTTP based controller does not register for liveness checkins
A few additional changes for fetching the Condition and Task objects
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commenting, but nothing here precludes a merge when ready.
} | ||
|
||
// state active | ||
if cond.State == condition.Active { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like we could smooth this interaction between Orchestrator and an HTTP client. Maybe condense this into a single interaction? I have some thoughts about implementing it, maybe I can get some time to help out.
this could be used by controllers regardless of how they are deployed (inband/oob)
This controller interfaces with the Orchestrator API to carry out Condition work and publish updates.