Split network-operator-agent into agent and worker #124
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces changes discussed in #121
Based on #110 and #112.
in this PR reconciler interfaces from #112 were renamed to
Adapters
and are now contained in separate packages. Additionally new podAgent
was added that uses theadapters
to configure the netwokring on the host. Based on gradual rollout #110, the workflow looks currently like this:network-operator-configurator
watches CRDs and creates per node config (NodeConfig
).network-operator-worker
pod watches forNodeConfigs
and if there is node config created for the node it serializes it and sends it via gRPC (localhost:50042
by default) to theagent
.Agent
(whcihc can be run as a pod or as standalone binary) is a gRPC server - it gets the config from theworker
and configures networking, and does perform configuration-specific healthchecks (e.g. checks if FRR is active).worker
gets success response form theagent
it's go on with common connectivity healthchecks and sets theNodeConfig
resource provisioning status.Update 02.10.2024: rebased to current gradual-rollout implementation.