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
lets see if there's a way to introspect the mcp to determine whether it has picked up the configs we've posted before unpausing it.
Maybe we won't be able to introspect all changes were picked up, but at least seeing that the changes we can check have been picked up gives us some assurance that the mcp has at least been updated.
This is mostly an optimization. The worst case scenario is we reboot a node twice to apply changes if we unpause too early.
The text was updated successfully, but these errors were encountered:
we don't create the MCP in the operator code anymore, so this is obsolete
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
from this discussion #25 (comment)
lets see if there's a way to introspect the mcp to determine whether it has picked up the configs we've posted before unpausing it.
Maybe we won't be able to introspect all changes were picked up, but at least seeing that the changes we can check have been picked up gives us some assurance that the mcp has at least been updated.
This is mostly an optimization. The worst case scenario is we reboot a node twice to apply changes if we unpause too early.
The text was updated successfully, but these errors were encountered: