<p>I have installed Eclipse Hono 1.1.1 Kubernetic cluster using Helm as per the below instructions.</p>
<p><a href="https://hub.helm.sh/charts/eclipse-iot/hono" rel="nofollow noreferrer">https://hub.helm.sh/charts/eclipse-iot/hono</a></p>
<p>Initially I tried to create a tenant using the below command</p>
<pre><code>curl -X POST &quot;http://servername:28080/v1/tenants/DEFAULT_TENANT123&quot; -H &quot;accept: application/json&quot; -H &quot;Content-Type: application/json&quot;
</code></pre>
<p>But then I got the Resource not found error.</p>
<p>And then as per the instructions in the <a href="https://stackoverflow.com/questions/34601650/how-do-i-run-curl-command-from-within-a-kubernetes-pod">How do i run curl command from within a Kubernetes pod</a></p>
<pre><code>curl -X POST &quot;http://ServiceName:Serviceport/v1/tenants/DEFAULT_TENANT123&quot; -H &quot;accept: application/json&quot; -H &quot;Content-Type: application/json&quot;
</code></pre>
<p>Again it dint work..!!!</p>
<p>I tried the following command to enter into the device registry pod</p>
<pre><code> kubectl exec -it honohelmdeploy-service-device-registry-0 -- sh
</code></pre>
<p>And inside the device registry pod, I tried to run the above command and still it dint work.</p>
<p>I am not sure what should be the Host and Port while using the below command</p>
<pre><code>curl -X POST &quot;http://HOST:PORT/v1/tenants/DEFAULT_TENANT123&quot; -H &quot;accept: application/json&quot; -H &quot;Content-Type: application/json&quot; 
</code></pre>
<p>I tried using device registry service name/ device registry pod name as hosts.
I tried using device registry ports
I tried using my server name / localhost as hosts..
I tried using 28080 as ports..</p>
<p>But I was not able to create a Tenant. Please assist.</p>
<p>Edited with the screeshot for kubectl get svc command
<a href="https://i.stack.imgur.com/YAVzF.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/YAVzF.jpg" alt="enter image description here" /></a></p>

<p>Ok, it seems like you have installed Hono to minikube without any loadbalancer running. You can see this from the <em>EXTERNAL-IP</em> column which contains <code>&lt;pending&gt;</code> for all of Hono's (externally visible) service endpoints.</p>

<p>You need to start <code>minikube tunnel</code> in order for these endpoints to be exposed via a loadbalancer as described in the chart's README. You should be able to run the <code>minikube tunnel</code> command either before or after having installed Hono to the cluster. Once the loadbalancer is running, the <em>EXTERNAL-IP</em> addresses should be bound and you should be able to access the service endpoints.</p>
