minikube 1.19.0 is namespace changed

[bringer1092]

This is a Bug Report

Problem:
Ingress namespace is minikube 1.19.0 chage the status kube-system to ingress-nginx.

Since the output result has also changed, I decided to display only one line.

minikube 1.19.0 Upgrade ingress addon files according to upstream.

https://github.com/kubernetes/minikube/blob/master/CHANGELOG.md#version-1190-beta0---2021-04-05
kubernetes/minikube#10879

Proposed Solution:

1. Verify that the NGINX Ingress controller is running

   minikube version 1.18.1 or earlier

   kubectl get pods -n kube-system

   minikube version 1.19.0 or later

   kubectl get pods -n ingress-nginx

   {{< note >}}This can take up to a minute.{{< /note >}}

   Output:

   minikube version 1.18.1 or earlier

   NAME                                        READY     STATUS    RESTARTS   AGE
   default-http-backend-59868b7dd6-xb8tq       1/1       Running   0          1m
   kube-addon-manager-minikube                 1/1       Running   0          3m
   kube-dns-6dcb57bcc8-n4xd4                   3/3       Running   0          2m
   kubernetes-dashboard-5498ccf677-b8p5h       1/1       Running   0          2m
   nginx-ingress-controller-5984b97644-rnkrg   1/1       Running   0          1m
   storage-provisioner                         1/1       Running 

   minikube version 1.19.0 or later

   NAME                                        READY   STATUS      RESTARTS   AGE
   ingress-nginx-admission-create-ckgpj        0/1     Completed   0          15m
   ingress-nginx-admission-patch-585xt         0/1     Completed   0          15m
   ingress-nginx-controller-5d88495688-b4s8m   1/1     Running     0          15m

Page to Update:
https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/

[tengqm]

/triage accepted

[Kartik494]

/assign

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Kartik494]

/remove-lifecycle stale