Kubernetes helm chart tries to connect to port 8080

[Phil Mead]

I am new to Kubernetes.
I am running Kubernetes microk8s under Ubuntu
I have a deployment for mysql 8.0 running.

When I iusse the command to install the helm chart - helm install my-ssg layer7/gateway --set-file "license.value=license.xml" --set "license.accept=true"

I get the following error:
Error: INSTALLATION FAILED: Kubernetes cluster unreachable: Get "http://localhost:8080/version": dial tcp 127.0.0.1:8080: connect: connection refused

Any ideas where I should look?

netstat shows no listener on port 8080. However, it says it is listening on https port 16443.

------------------------------
Phil Mead
------------------------------

[Gary Vermeulen]

Hey Phil,

It looks like you're missing your kubeconfig file. Kubectl and Helm use the same configuration file by default.

Microk8s comes packaged with its own kubectl - there's also a helm3 add-on that you can enable (I would recommend adding metallb).

$ microk8s kubectl get pods

$ microk8s config ==> shows the kubeconfig file

Once you've confirmed everything is working as expected you can copy the config over to your local kube config directory. This link goes through the configuration in more detail.

Let me know if that works or if you have any more questions.

[Phil Mead]

Thank you. That fixed my problem.

I did the following:
# cd $HOME
# mkdir .kube (if necessary)
# cd .kube
# microk8s config > config

Phil Mead

Client Services Consultant | Services Resident

Open Group Master Certified IT Architect
<https: www.opengroup.org/openprofessions/certificates/op.html?pcid="CA96103">
Broadcom

mobile: [phone]
1900 Reston Metro Plaza # 6 | Reston, VA 20190
[e-mail] | broadcom.com



On Mon, May 8, 2023 at 8:27 PM Gary Vermeulen via Broadcom <
[e-mail]> wrote:

> Hey Phil, It looks like you're missing your kubeconfig file. Kubectl and
> Helm use the same configuration file by default. Microk8s comes... -posted
> to the "Layer7 API Management" community
> [image: Broadcom] <https: community.broadcom.com="">
> Layer7 API Management
> <https: community.broadcom.com/enterprisesoftware/communities/community-home/digestviewer?communitykey="0f580f5f-30a4-41de-a75c-e5f433325a18">
> Post New Message <[e-mail]>
> Re: Kubernetes helm chart tries to connect to port 8080
> <https: community.broadcom.com/enterprisesoftware/discussion/kubernetes-helm-chart-tries-to-connect-to-port-8080#bmf2d7ca95-6705-4441-8fac-0187fd5f61fb="">
> Reply to Group
> <b[e-mail]?subject=re:+kubernetes+helm+chart+tries+to+connect+to+port+8080> Reply
> to Sender
> <https: community.broadcom.com/enterprisesoftware/communities/all-discussions/postreply?messagekey="f2d7ca95-6705-4441-8fac-0187fd5f61fb&ListKey=50bda2ce-ba50-4aa1-8823-1f58a1cf543e&SenderKey=b9f57345-2c7c-40d4-bf3c-71fa84ea8290">
> [image: Gary Vermeulen]
> <https: community.broadcom.com/network/members/profile?userkey="b9f57345-2c7c-40d4-bf3c-71fa84ea8290">
> May 8, 2023 8:27 PM
> Gary Vermeulen
> <https: community.broadcom.com/network/members/profile?userkey="b9f57345-2c7c-40d4-bf3c-71fa84ea8290">
>
> Hey Phil,
> It looks like you're missing your kubeconfig file. Kubectl and Helm use
> the same configuration file by default.
> Microk8s comes packaged with its own kubectl - there's also a helm3 add-on
> that you can enable (I would recommend adding metallb).
> $ microk8s kubectl get pods
> $ microk8s config ==> shows the kubeconfig file
> Once you've confirmed everything is working as expected you can copy the
> config over to your local kube config directory. This
> <https: microk8s.io/docs/working-with-kubectl=""> link goes through the
> configuration in more detail.
> Let me know if that works or if you have any more questions.
> *Reply to Group Online
> <https: community.broadcom.com/enterprisesoftware/communities/all-discussions/postreply?messagekey="f2d7ca95-6705-4441-8fac-0187fd5f61fb&ListKey=50bda2ce-ba50-4aa1-8823-1f58a1cf543e">*
> *Reply to Group via Email
> <b[e-mail]?subject=re:+kubernetes+helm+chart+tries+to+connect+to+port+8080>*
> *View Thread
> <https: community.broadcom.com/enterprisesoftware/discussion/kubernetes-helm-chart-tries-to-connect-to-port-8080#bmf2d7ca95-6705-4441-8fac-0187fd5f61fb="">*
> *Recommend
> <https: community.broadcom.com:443/enterprisesoftware/discussion/kubernetes-helm-chart-tries-to-connect-to-port-8080?messagekey="f2d7ca95-6705-4441-8fac-0187fd5f61fb&cmd=rate&cmdarg=add#bmf2d7ca95-6705-4441-8fac-0187fd5f61fb">*
> *Forward
> <https: community.broadcom.com/enterprisesoftware/communities/all-discussions/forwardmessages?messagekey="f2d7ca95-6705-4441-8fac-0187fd5f61fb&ListKey=50bda2ce-ba50-4aa1-8823-1f58a1cf543e">*
> *Flag as Inappropriate
> <https: community.broadcom.com/enterprisesoftware/discussion/kubernetes-helm-chart-tries-to-connect-to-port-8080?markappropriate="f2d7ca95-6705-4441-8fac-0187fd5f61fb#bmf2d7ca95-6705-4441-8fac-0187fd5f61fb">*
>
> -------------------------------------------
> Original Message:
> Sent: May 08, 2023 04:39 PM
> From: Phil Mead
> Subject: Kubernetes helm chart tries to connect to port 8080
>
> I am new to Kubernetes.
> I am running Kubernetes microk8s under Ubuntu
> I have a deployment for mysql 8.0 running.
>
> When I iusse the command to install the helm chart - helm install my-ssg
> layer7/gateway --set-file "license.value=license.xml" --set
> "license.accept=true"
>
> I get the following error:
> Error: INSTALLATION FAILED: Kubernetes cluster unreachable: Get "
> localhost:8080/version": <http: localhost:8080/version=""> dial tcp
> 127.0.0.1:8080: connect: connection refused
>
> Any ideas where I should look?
>
> netstat shows no listener on port 8080. However, it says it is listening
> on https port 16443.
>
>
>
>
> ------------------------------
> Phil Mead
> ------------------------------
>
>
>
>
> You are subscribed to "Layer7 API Management" as [e-mail].
> To change your subscriptions, go to My Subscriptions
> <http: community.broadcom.com/preferences?section="Subscriptions">. To
> unsubscribe from this community discussion, go to Unsubscribe
> <http: community.broadcom.com/higherlogic/egroups/unsubscribe.aspx?userkey="17f5279e-3def-458e-95be-0187145765e8&sKey=KeyRemoved&GroupKey=50bda2ce-ba50-4aa1-8823-1f58a1cf543e">.
>
>
> Copyright © 2005-2023 Broadcom. All Rights Reserved. The term "Broadcom"
> refers to Broadcom Inc. and/or its subsidiaries.
>
> Hosted by Higher Logic, LLC on the behalf of Broadcom - Privacy Policy
> <https: www.broadcom.com/company/legal/privacy-policy=""> | Cookie Policy
> <https: www.higherlogic.com/legal/privacy=""> | Supply Chain Transparency
> <https: www.broadcom.com/company/citizenship/governance-and-ethics#supply="">
> | Terms of Use <http: termsandconditions="">
>

--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.