charm is constantly logging errors

### Bug Description

the charm gets into this state wheres logging tls errors and it stays active idle. Its not working as expected and is not injecting configs specified in its `settings_yaml` config to the other pods (in the corresponding namespaces.)

There is no proper visibility into the state of this charm outside of logs. It would be nice if the charm workload status reflected its state and it could forward its logs to COS(loki).

### To Reproduce

N/A

### Environment

```
namespace-node-affinity active 1 namespace-node-affinity 0.1/beta 5 REDACTED no
```

### Relevant Log Output

```shell
2024/01/29 1835 http: TLS handshake error from REDACTED remote error: tls: bad certificate
2024/01/29 1838 http: TLS handshake error from REDACTED remote error: tls: bad certificate
2024/01/29 1840 http: TLS handshake error from REDACTED remote error: tls: bad certificate
2024/01/29 1842 http: TLS handshake error from REDACTED remote error: tls: bad certificate
2024/01/29 1857 http: TLS handshake error from REDACTED remote error: tls: bad certificate
2024/01/29 1857 http: TLS handshake error from REDACTED remote error: tls: bad certificate
2024/01/29 1857 http: TLS handshake error from REDACTED remote error: tls: bad certificate
2024/01/29 1836 http: TLS handshake error from REDACTED remote error: tls: bad certificate
2024/01/29 1805 http: TLS handshake error from REDACTED remote error: tls: bad certificate
```

### Additional Context

`settings_yaml` config
```yaml
controller-k8s: |
nodeSelectorTerms:
- matchExpressions:
- key: kubeflowserver
operator: In
values:
- true
kubeflow: |
nodeSelectorTerms:
- matchExpressions:
- key: kubeflowserver
operator: In
values:
- true
metallb: |
nodeSelectorTerms:
- matchExpressions:
- key: kubeflowserver
operator: In
values:
- true
```