Deploying a pod to Minikube Cluster does not offer a route or service exposing the application deployed

[odockal]

Bug description

I was trying to deploy to a simple application into a minikube cluster. There are some things requiring the improvements.

1. Deploy To Kubernetes with minikube context shows kind specific ingress controller option in the form (app will be available on localhost:9090 text) - I am not sure if that is intended or not
2. If the app is deployed this way, it gets into the cluster, but nothing is available on localhost:9090 (as obviously there is no project contour controller in the minikube cluster)
3. It requires me to go to the cli and run something like: minikube service flask-mini-8000 --url

So I believe this could be bug/enhancement request. Bug is that we are showing kind stuff, enhancement could be that we want to also offers a service to be exposed.

Operating system

Windows 10

Installation Method

Installer from website/GitHub releases

Version

1.6.0

Steps to reproduce

1. have a working pod with exposed port ie. httpd-24 or flask
2. Install minikube
3. Create a minikube cluster
4. Switch to minikube context
5. Deploy pod to kubernetes
6. Assert: Pod is deployed to the cluster
7. Assert: Application is accessible from host machine
   Actual result: pod is deployed, I am seeing ingress option in the form - which is incorrect, no service is exposed, requires manual step

Relevant log output

No response

Additional context

No response

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 6 months. It will be closed in 30 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant. Thank you for your contributions!