You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 9, 2023. It is now read-only.
Framework or not we need to refactor kube-valet to use dependency injection. There are now two different sources of update events one from the watches and one from the mutating webhooks. both of these places should call a controller and not have custom code. This turns the dependency tree into a DAG so we need to handle that appropriately.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Framework or not we need to refactor kube-valet to use dependency injection. There are now two different sources of update events one from the watches and one from the mutating webhooks. both of these places should call a controller and not have custom code. This turns the dependency tree into a DAG so we need to handle that appropriately.
The text was updated successfully, but these errors were encountered: