Add hostNetwork setting for agent deployment policy #2659
Merged
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.
Refers to rancher-sandbox/cluster-api-addon-provider-fleet#74
Fleet agent can be used to deploy bundles during cluster bootstrap procedure. One common operation is to deploy CNI configuration. While it is possible, current fleet-agent config is not getting scheduled on the cluster due to dependency on the CNI itself.
To avoid it, a user may want to specify
spec.hostNetwork
setting on theCluster
resource. This allows the init pod to proceed further and register the agent on the management cluster, so it can proceed with applications rollout.