<p>I'm running colima with kubernetes like:
<code>colima start --kuberenetes</code></p>
<p>I created a few running pods, and I want to see access the through the browsers.
But I don't know what is the colima IP (or kubernetes node IP).</p>
<p>help appreciated</p>

Tzook Bar Noy
<p>You can get the nodeIp so:</p>
<pre><code>kubectl get node

NAME       STATUS   ROLES    AGE   VERSION
nodeName   Ready    &lt;none&gt;   15h   v1.26.0
</code></pre>
<p>Then with the nodeName:</p>
<pre><code>kubectl describe node nodeName
</code></pre>
<p>That gives you a descrition of the node and you should look for this section:</p>
<pre><code>Addresses:
  InternalIP:  10.165.39.165
  Hostname:    master
</code></pre>
<p>Ping it to verify the network.</p>
<p>Find your host file on Mac and make an entry like:</p>
<pre><code>10.165.39.165 test.local
</code></pre>
<p>This let you access the cluster with a domain name.</p>
<p>Ping it to verify.</p>
<p>You can not access from outside the cluster a ClusterIp.
To access your pod you  have several possibilities.</p>
<ol>
<li>if your service is type ClusterIp, you can create a temporary connection from your host with a port forward.</li>
</ol>
<pre><code>kubectl port-forward svc/yourservicename localport:podport
</code></pre>
<ol start="2">
<li>(i would raccomend this) create a service type: NodePort</li>
</ol>
<p>Then</p>
<pre><code>kubectl get svc -o wide
</code></pre>
<p>Shows you the NodePort: between(30000-32000).</p>
<p>You can access now the Pod by: test.local:nodePort or Ipaddress:NodePort.</p>
<p>Note: If you deployed in a namespace other than default, add -n yournamespace in the kubectl commands.</p>
<p>Update:</p>
<p>if you want to start colima with an ipAddress, first find one of your local network which is available.</p>
<p>Your network setting you can get with:</p>
<pre><code>ifconfig
</code></pre>
<p>find the network. Should be the same of that of your Internet router.</p>
<p>Look for the subnet. Most likely 255.255.255.0.</p>
<p>The value to pass then:</p>
<pre><code>  --network-address xxx.xxx.xxx.xxx/24
</code></pre>
<p>In case the subnet is 255.255.0.0 then /16. But i dont think, if you are connect from home. Inside a company however this is possible.</p>
<p>Again check with ping and follow the steps from begining to verify the kubernetes node configuration.</p>
