"Could not stabilize" and "could not map pods to service... no pods match service..." errors coming up consistently

### Expected behavior

Running `skaffold dev --port-forward` or `skaffold dev --port-forward --status-check=false` should start-up the cluster.

### Actual behavior

As of the two weeks, or so, I started getting `could not stabilize with 2m0s` when I needed to restart the cluster. Seems like 4 out of 5 times I would get it.

Started running with `--status-check-false` and I'm getting a bunch of:
```
WARN[0207] could not map pods to service default/admin-new-cluster-ip-service-dev/3000: no pods match service admin-new-cluster-ip-service-dev/3000
```
`CTRL+C`, retry a few times, and eventually things start up normally.

Checking `minikube dashboard` and for a while it seemed like it was taking upwards of a minute for Pods, Deployments, Serviecs to be destroyed, but I've looked at it about a dozen times and now they are being destroyed within a few seconds of `CTRL + C`.

### Information

- Skaffold version: 1.14.0
- Minikube version: 1.13.1
- Operating system: macOS 10.15.5-10.15.7; Pop!_OS 20.04... seems to happen more frequently on macOS so I'm tempted to switch back to Linux.
- Contents of skaffold.yaml:
```
apiVersion: skaffold/v2beta1
kind: Config
build:
artifacts:
- image: companyapp.azurecr.io/company-app-admin-new
context: admin-new
sync:
manual:
- src: 'src/**/*.js'
dest: .
- src: 'src/**/*.jsx'
dest: .
- src: '**/*.json'
dest: .
- src: 'public/**/*.html'
dest: .
- src: 'src/assets/sass/**/*.scss'
dest: .
- src: 'src/build/**/*.js'
dest: .
docker:
dockerfile: Dockerfile.dev
local:
push: false
deploy:
kubectl:
manifests:
- manifests/dev/ingress.yaml
- manifests/dev/admin-new.yaml
```