Sidecar injection fail for default namespace on microk8s

When filing a bug, please include the following headings if possible. Any example text in this template can be deleted.

#### Overview of the Issue
Running 1 node microk8s behind traefik. Consul inject multiple application for service mesh in default namespace 'kube-system'

A paragraph or two about the issue you're experiencing.

Unable to detect service in default namespace 'kube-system' Create new ns 'consul-system' and works fine

#### Reproduction Steps

Steps to reproduce this issue, eg:

1. Create a cluster with n client nodes n and n server nodes
1. Run `curl ...`
1. View error

### Consul info for both Client and Server

Client info

```
output from client 'consul info' command here
```

Server info

```
output from server 'consul info' command here
```

### Operating system and Environment details

OS, Architecture, and any other information you can provide about the environment.

### Log Fragments

Include appropriate Client or Server log fragments. If the log is longer than a few dozen lines, please include the URL to the [gist](https://gist.github.com/) of the log instead of posting it in the issue. Use `-log-level=TRACE` on the client and server to capture the maximum log detail.

The report names a single-node MicroK8s cluster behind Traefik and a Consul sidecar-injection failure in the kube-system namespace, but provides no source files, tests, logs, or complete reproduction steps. Start by reproducing injection in kube-system and in the working consul-system namespace; done means applications are detected and injected successfully in the default namespace.

Written by the indexing model from the issue text.