docs(k3s): add back the flag to disable network policies

[rio]

This was actually added in #13783 but got removed again after some other changes.
That flag is required because otherwise any liveness or readiness probes will be classified as world traffic and get
dropped if network policies are installed.

Signed-off-by: Rio Kierkels riokierkels@gmail.com

[qmonnet]

The commit that removed this flag described it as “unrecognized”? #15503
@aanm do you have more context?

[rio]

I just now notice that it's removing it from the agent and it was never set for the server. In that case that commit is correct because the agent doesn't support that flag only the server does.

[aanm]

@qmonnet yes, I just copy-paste the original PR from #15191

[qmonnet]

Ok, if this is a matter of passing the option to the correct entity then fine by me.

/Cc @seanmwinn for a quick review, as he is more familiar with the topic.

[seanmwinn]

I just now notice that it's removing it from the agent and it was never set for the server. In that case that commit is correct because the agent doesn't support that flag only the server does.

Ok, if this is a matter of passing the option to the correct entity then fine by me.

/Cc @seanmwinn for a quick review, as he is more familiar with the topic.

I'm not particularly familiar with this topic as many of the flags for k3s have changed since we initially published a k3s getting started guide. I would need to test this to validate the reported behavior as well as the fix.

[qmonnet]

@seanmwinn Thanks, I thought maybe you knew about that option. If you need to run tests but don't have cycles for this at the moment, I think we should just go ahead and merge the PR. After all, this is simply a documentation change adding one option back.

I'll mark the PR as ready-to-merge. Thanks!