Activate auto registration token by default and update docs on authentication

[srkoster]

• Activated auto registration by default so the charts works with the default values.yaml (fix for Agents CrashLoopBackOff with 0.16.0 ("machine not validated"), but work with 0.15.0 #228)
• Added documentation on authentication, including auto registration, TLS client authentication and flushing old machines (fix for agents re-register when restarting daemonset #230)
• Removed auto registration token from Appsec documentation (moved into authentication)
• Fixed a few typos

[github-actions]

@srkoster: There are no 'kind' label on this PR. You need a 'kind' label to generate the release automatically.

• /kind feature
• /kind enhancement
• /kind fix
• /kind chore
• /kind dependencies

Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the forked project rr404/oss-governance-bot repository.

[github-actions]

@srkoster: There are no area labels on this PR. You can add as many areas as you see fit.

• /area agent
• /area local-api
• /area cscli
• /area security
• /area configuration

Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the forked project rr404/oss-governance-bot repository.

[srkoster]

/kind enhancement
/area configuration

[mmetc]

Hello @srkoster

thanks for the contribution!

Is there a specific reason to remove the 192.168 network?

[srkoster]

@mmetc I removed 192.168 because it is used a lot for home LANs and then introduces a risk of overlap when being used for the Kubernetes network as well. Therefore I suspect that not many people are using it and I would rather keep the default list short / restrictive (to prevent auto registration from outside the Kubernetes network). They are however free to add the range to their own config.

[mmetc]

Look good to me but I would prefer to put the network back, I personally have created clusters with class A, B or C ranges and don't have data for how our users are configuring them

[srkoster]

@mmetc that's fair. I've put the range back in the values.yaml and the readme.

[mmetc]

Thanks @srkoster!