Write peer config to secret instead of status

[paddyoneill]

trafficstars

Is your feature request related to a problem? Please describe. Currently the peer config is wrote to the status as a template that needs to be piped to bash to insert the private key. Having the complete peer config reconciled to a secret would be more inline with standard Kubernetes design patterns.

Describe the solution you'd like Remove the peer config template from the status field, and write it to a secret.

[jodevsa]

thanks!