plese solve my problem of connecting minikube cluster to lens

[AyushAnand30]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• Lens Version:
• OS: [e.g. OSX]
• Installation method (e.g. snap or AppImage in Linux):

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:

Your logs go here...

Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.

your kubeconfig here

Additional context
Add any other context about the problem here.

[Tixon123]

Hello AyushAnand30,

Thank you for reaching out to Lens support!

Thank you for reporting a bug.

We are working on your issue. Stand by for further updates.

Best Regards,
Tikhon Kudinov
Lens Support Engineer
Mirantis, Inc

[Tixon123]

Hello AyushAnand30,

As you can see on the screenshot error: "the path to client cert doesn’t exist"

That's the main issue.

Best Regards,
Tikhon Kudinov
Lens Support Engineer
Mirantis, Inc

[AyushAnand30]

Please give me a favour and spacify each steps how can i solve this problem

…

On Wed, 4 Sept, 2024, 16:43 Tixon123, ***@***.***> wrote: Hello AyushAnand30, As you can see on the screenshot error: "the path to client cert doesn’t exist" That's the main issue. Best Regards, Tikhon Kudinov Lens Support Engineer Mirantis, Inc — Reply to this email directly, view it on GitHub <#8085 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJ6STVGUFF5EJ7NCJZUWJYLZU3TORAVCNFSM6AAAAABNT4RLBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRYGYZDIOBWGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>