Minikube on Apple MacBook Pro M2 - Ingress-DNS issue crashing

[cirix]

What Happened?

Hi all,
I installed minikube and also aligned and made sure that the ingress and ingress-dns plugins are using teh arm64 version of the relevant software.
Also I configured my dns to point to ingress dns and I have disabled firewalling.
The configuration of the DNS on MacOSX is a bit different as you have to do it using scutil, which was properly implemented.
Once I have the system up and running and my services deployed, when I try to access from browser one of m ingress services using the typical ingress-dns, the pod fails and goes in an endless restart and never revives . I had it working sporadically, but I can't see to make it work consistently.
On top, on minikube looks like the ingress-dns is nothing but a dns2 javascript dns server that is configured to receive traffic, but looks like the gitlab repository that cryptexlab has is not updated the last 4 years.
What are the alternatives proposed from the community? Expose the core-dns and create a custom resolver for dns even if the port is not the standard 53 but the one shared when configuring the service to type loadbalancer?

Attach the log file

logs.txt

Operating System

macOS (Default)

Driver

QEMU

[cirix]

Update to @ALL I have cloned the repo of minikube-ingress-dns from gitlab and the build succeeds, I plan offering support and evolution. Already I patched the versions of deps and also updated the version of the API from v1beta1 to v1.
My plan is to offer that as part of the addons, if my pr is accepted and offer evolution on the ingress dns, and extend it with gateway api too, as currently there is no alternative. I would like to know if there will be traction there.

br
Nik

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.