Is it possible to select network interface(eth0, eth1, ens192 etc.) in none driver?

[m18unet]

What Happened?

I have two network interfaces on my computer. Their names are eth0 and eth1.

+--------------------------------------------------+
|                     My Computer                  |
|                                                  |
|  eth0                                       eth1 |
|   +                                          +   |
+--------------------------------------------------+
    |                                          |
    |                                          |
    |                                          |
    |                                          |
    v                                          v
10.10.22.50                               192.168.29.50
(minikube selects it automatically)       (I want you to select this)

eth0 network interface is selected automatically when I start minikube with the following command: (I prefer none driver for some special reasons.)

$ sudo -E minikube start \
  --driver=none \
  --kubernetes-version=1.24.3 \
  --container-runtime=docker \

$ minikube ip
10.10.22.50

I want to select eth1 network interface(192.168.29.50). Is this possible?

Attach the log file

N/A

Operating System

Ubuntu

Driver

--driver=none

[RA489]

/kind support

[vonProteus]

I would also like to know the answer to this question
@m18unet did you find a solution to this problem?

[afbjorklund]

Currently the node IP comes from ChooseHostInterface, which I think chooses the one with the gateway.

// GetIP returns an IP or hostname that this host is available at
func (d *Driver) GetIP() (string, error) {
        ip, err := knet.ChooseHostInterface()
        if err != nil {
                return "", err
        }
        return ip.String(), nil
}

https://pkg.go.dev/k8s.io/apimachinery@v0.25.3/pkg/util/net#ChooseHostInterface

In the original docker-machine, it was a flag (confusingly called --url)

[m18unet]

I would also like to know the answer to this question
@m18unet did you find a solution to this problem?

@vonProteus

Unfortunately, I couldn't find a solution.

[m18unet]

Currently the node IP comes from ChooseHostInterface, which I think chooses the one with the gateway.

// GetIP returns an IP or hostname that this host is available at
func (d *Driver) GetIP() (string, error) {
        ip, err := knet.ChooseHostInterface()
        if err != nil {
                return "", err
        }
        return ip.String(), nil
}

https://pkg.go.dev/k8s.io/apimachinery@v0.25.3/pkg/util/net#ChooseHostInterface

In the original docker-machine, it was a flag (confusingly called --url)

@afbjorklund

Thank you very much for your reply. I don't think there is a solution for now. Am I right?

[afbjorklund]

Only workarounds*, as far as I know. All flags are hardcoded in the minikube "registry"

• none driver uses k8s.io/apimachinery/pkg/util/net.ChooseHostInterface() for apiserver IP, causing problems for laptops on DHCP #14035

• https://github.com/kubernetes/minikube/blob/master/pkg/minikube/registry/drvs/none/none.go

So it needs to have a new flag for the IP, and then propagate that to the "none2" driver:

• https://github.com/docker/machine/blob/master/drivers/none/driver.go

• https://github.com/kubernetes/minikube/blob/master/pkg/drivers/none/none.go

[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

[m18unet]

/remove-lifecycle stale

[m18unet]

Anything worth noting?

[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/test-infra repository.