Harpreet singh

hi @miekg @chrisohaver I would like to pick up this issue to work on and want to contribute and learn from this awesome project. I have been doing some research...

Hi @longwuyuan I have added the relevant information as requested. kubectl get all,ing -A -o wide ``` NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES default...

>(1) Your services of --LoadBalancer are in pending state so while I see some of your URL are internal to cluster, I would not trust any of the data presented...

kubectl cluster-info ``` Kubernetes control plane is running at https://127.0.0.1:60297 CoreDNS is running at https://127.0.0.1:60297/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy ``` kubectl logs ingress-nginx-controller-5689d5bcd6-sq957 -n ingress-nginx ``` ------------------------------------------------------------------------------- NGINX Ingress controller Release: 1.0.0-dev Build: git-771ce1c6d...

@longwuyuan Yes sure. I can write the e2-test. I am familiarizing myself with the way the e2e test are structured as I am new to project. Thank you very much...

@longwuyuan Added one e2e test case. Have a look and let me know your thoughts. 

@longwuyuan Thank you too for guiding through the process.

Hi @pacoxu I was looking at the test cases for prune inside `apply_test.go`, seems like it never goes inside the pruning logic. https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/kubectl/pkg/cmd/apply/apply_test.go#L584-L632 as we are not setting up `fakeDynamicClient`...

Hi @benfry Hope you are doing well. I saw in your [commit](https://github.com/processing/processing4/commit/1849ab76bcd1d10bee397c99775efd3415f4fa4b#diff-6abc5b99da96e317f0754499132ed82a1980faddf44317647b2a5e35d6c817d3R17-R19) that you have included this pull request in `todo.txt`. Does it mean you're going to have a look...

Yes, that make sense.. I was also curious why `| key` was done in first place. Testing it more thoroughly make sense.