status-set called on every kubeconfig write

[Mike Wilson]

unit-kubernetes-master-0: 20:49:38 INFO unit.kubernetes-master/0.juju-log Invoking reactive handler: reactive/kubernetes_master.py:795:send_data
unit-kubernetes-master-0: 20:49:38 INFO unit.kubernetes-master/0.juju-log Invoking reactive handler: reactive/kubernetes_master.py:1006:create_self_config
unit-kubernetes-master-0: 20:49:38 INFO unit.kubernetes-master/0.juju-log status-set: maintenance: Writing kubeconfig file.
...
unit-kubernetes-master-0: 20:54:32 INFO unit.kubernetes-master/0.juju-log Invoking reactive handler: reactive/kubernetes_master.py:1006:create_self_config
unit-kubernetes-master-0: 20:54:32 INFO unit.kubernetes-master/0.juju-log status-set: maintenance: Writing kubeconfig file.
...
unit-kubernetes-master-0: 21:00:10 INFO unit.kubernetes-master/0.juju-log Invoking reactive handler: reactive/kubernetes_master.py:1006:create_self_config
unit-kubernetes-master-0: 21:00:10 INFO unit.kubernetes-master/0.juju-log status-set: maintenance: Writing kubeconfig file.

[Peter Jose De Sousa (pjds)]

https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/33

[Kevin W Monroe (kwmonroe)]

The original impl had to be partially reverting because we missed a few things in data_changed that kept us from writing an accurate kubeconfig:

https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/41

The scope of this fix is now limited to replacing the expensive status_set with debug log message.

[Kevin W Monroe (kwmonroe)]

Follow-up bug to address the unnecessary writes:

https://bugs.launchpad.net/charm-kubernetes-master/+bug/1837930

[George Kraft (cynerva)]

Cherry-picked to stable:

https://github.com/charmed-kubernetes/charm-kubernetes-master/commit/d3e8d8c5e9ca1685c2f9590d2deaeb82af7f84cc
https://github.com/charmed-kubernetes/charm-kubernetes-master/commit/a565726b64858721f8cf66df766bebacff084439