--- title: Charmhub | Deploy Canonical Observability Stack Lite using Charmhub - The Open Operator Collection description: Deploy the latest version of Canonical Observability Stack Lite on any cloud. url: https://charmhub.io/cos-lite/docs/how-to/troubleshoot-gateway-address-unavailable --- ##### We've discontinued the registration of new Bundles New Bundle registrations are no longer accepted. Existing bundles remain functional. We recommend using the Juju Terraform Provider for new deployments. [Learn more](https://discourse.charmhub.io/t/discontinuing-new-charmhub-bundle-registrations/15344) # Canonical Observability Stack Lite [Canonical Observability](https://charmhub.io/publisher/observability "View all packages from Canonical Observability") | bundle * [Canonical Observability](https://charmhub.io/publisher/observability "View all packages from Canonical Observability") | bundle Platform: stable 26 ``` juju deploy cos-lite ``` [Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications) --- #### Relevant links * [Homepage](https://github.com/canonical/cos-lite-bundle) --- #### Contacts * [Submit a bug](https://github.com/canonical/cos-lite-bundle/issues) --- Share your thoughts on this charm with the community on discourse. [Join the discussion](https://discourse.charmhub.io/) --- [Add docs to a charm](https://juju.is/docs/sdk/add-docs-to-your-charmhub-page) Our docs have moved to a new home! * [Traefik K8s documentation](https://documentation.ubuntu.com/traefik-k8s-charm/latest/) Please update your bookmarks, and [contact us](https://matrix.to/#/#charmhub-charmdev:ubuntu.com) if you have any questions. Whenever Traefik is used to ingress your Kubernetes workloads, you risk encountering the dreaded “Gateway Address Unavailable” message. In this article, we’ll go through what you can do to remediate it. #### Assumes MicroK8s In this article, we will assume that you are running MicroK8s on either a bare-metal or virtual machine. If your setup differs from this, parts of the how-to may still apply, although you will need to tailor the exact steps and commands to your setup. ## [Checklist](https://charmhub.io/cos-lite/docs/how-to/troubleshoot-gateway-address-unavailable#p-25874-checklist) * You have ran `juju trust --scope=cluster` * The [metallb microk8s addon](https://microk8s.io/docs/addon-metallb) is enabled. * Traefik’s service type is `LoadBalancer`. * An external IP address is assigned to traefik. ## [The metallb addon isn’t enabled](https://charmhub.io/cos-lite/docs/how-to/troubleshoot-gateway-address-unavailable#p-25874-the-metallb-addon-isnt-enabled) Check with: ``` microk8s status -a metallb ``` If it is disabled, you can enable it with: ``` IPADDR=$(ip -4 -j route get 2.2.2.2 | jq -r '.[] | .prefsrc') microk8s enable metallb:$IPADDR-$IPADDR ``` This command will fetch the IPv4 address assigned to your host, and hand it to MetalLB as an assignable IP. If the address range you want to hand to MetalLB differs from your host ip, alter the `$IPADDR` variable to instead specify the range you want to assign, for instance `IPADDR=10.0.0.1-10.0.0.100`. ## [No external IP address is assigned to the traefik service](https://charmhub.io/cos-lite/docs/how-to/troubleshoot-gateway-address-unavailable#p-25874-no-external-ip-address-is-assigned-to-the-traefik-service) Does the traefik service have an external IP assigned to it? Check with: ``` JUJU_APP_NAME="traefik" kubectl get svc -A -o wide | grep -E "^NAMESPACE|$JUJU_APP_NAME" ``` ## [No available IP in address pool](https://charmhub.io/cos-lite/docs/how-to/troubleshoot-gateway-address-unavailable#p-25874-no-available-ip-in-address-pool) This frequently happens when: * Metallb has only one IP in its range but you deployed two instances of traefik, or traefik is forcefully removed (`--force --no-wait`) and then a new traefik app is deployed immediately after. * The [`ingress`](https://microk8s.io/docs/ingress) addon is enabled. It’s possible that nginx from the ingress addon has claimed the ExternalIP. Disable nginx and re-enable metallb. Check with: ``` kubectl get ipaddresspool -n metallb-system -o yaml && kubectl get all -n metallb-system ``` You could add more IPs to the range: ``` FROM_IP="..." TO_IP="..." microk8s enable metallb:$FROM_IP-$TO_IP ``` ## [Juju reverted the service type to `ClusterIP`](https://charmhub.io/cos-lite/docs/how-to/troubleshoot-gateway-address-unavailable#p-25874-juju-reverted-the-service-type-to-clusterip) Juju controller cycling may cause the type to revert from `LoadBalancer` back to `ClusterIP`. Check with: ``` kubectl get svc -A -o wide | grep -E "^NAMESPACE|LoadBalancer" ``` If traefik isn’t listed (it’s not `LoadBalancer`), then recreate the pod to have it retrigger the assignment of the external IP with `kubectl delete` . It should be `LoadBalancer` when kubernetes brings it back. ## [Integration tests pass locally but fail on GitHub runners](https://charmhub.io/cos-lite/docs/how-to/troubleshoot-gateway-address-unavailable#p-25874-integration-tests-pass-locally-but-fail-on-github-runners) This used to happen when the github runners were at peak usage, making the already small 2cpu7gb runners run even slower. As much of a bad answer as this is, the best response may be to increase timeouts or try to move CI jobs to internal runners. ## [Verification](https://charmhub.io/cos-lite/docs/how-to/troubleshoot-gateway-address-unavailable#p-25874-verification) Verify that the Traefik Kubernetes service now has been assigned an external IP: ``` $ microk8s.kubectl get services -A NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) cos traefik LoadBalancer 10.152.183.130 10.70.43.245 80:32343/TCP,443:30698/TCP 4d3h 👆 - This one! ``` Verify that Traefik is functioning correctly by trying to trigger one of your ingressed paths. If you have COS Lite deployed, you may check that if works as expected using the Catalogue charm: ``` $ curl http:///-catalogue/ # for example... $ curl http://10.70.43.245/cos-catalogue/ ``` This command should return a long HTML code block if everything works as expected. ---