# Configuring github URL when enabling add-ons

**URL:** <https://discuss.kubernetes.io/t/configuring-github-url-when-enabling-add-ons/17184>\
**Category:** microk8s\
**Created:** [August 24, 2021, 12:41am UTC](https://discuss.kubernetes.io/t/configuring-github-url-when-enabling-add-ons/17184 "2021-08-24T00:41:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![flipcode](https://avatars.discourse-cdn.com/v4/letter/f/848f3c/32.png) [@flipcode](https://discuss.kubernetes.io/u/flipcode)\
**Post date:** [August 24, 2021, 12:41am UTC](https://discuss.kubernetes.io/t/configuring-github-url-when-enabling-add-ons/17184/1 "2021-08-24T00:41:54Z")

</div>

Hi,

I have some servers that are mandatorily not allowed to connect to the internet either directly or via a proxy. We have internal GitHub and Docker registry services and I have been able to pull all required images via the containerd registry mirrors.

I now need to enable prometheus and I can see that it tries to pull the repo from [github.com](http://github.com)…

```auto
[root@server1:current/]# microk8s enable prometheus
Addon dns is already enabled.
Fetching kube-prometheus version v0.8.0.
  % Total % Received % Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed
  0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: github.com
[root@server1:current/]# pwd
/var/snap/microk8s/current
[root@server1:current/]#

```

I can see this is configured in a RO file here:

```auto
[root@server1:actions/]# ls -lah /var/lib/snapd/snap/microk8s/2399/actions/enable.prometheus.sh
-rwxr-xr-x. 1 root root 3.2K Aug 12 19:55 /var/lib/snapd/snap/microk8s/2399/actions/enable.prometheus.sh
[root@server1:actions/]#

```

I can see in `/var/log/secure` the curl command:

```auto
[root@server1:actions/]# grep curl /var/log/secure | tail -1
2021-08-24T10:32:58.928693+10:00 server1 sudo: root : TTY=pts/0 ; PWD=/opt/apps/snap/microk8s/2399 ; USER=root ; ENV=LD_LIBRARY_PATH=/snap/microk8s/2399/lib:/snap/microk8s/2399/usr/lib:/snap/microk8s/2399/lib/x86_64-linux-gnu:/snap/microk8s/2399/usr/lib/x86_64-linux-gnu ; COMMAND=/snap/microk8s/2399/usr/bin/curl --cacert /snap/core18/current/etc/ssl/certs/ca-certificates.crt -L https://github.com/prometheus-operator/kube-prometheus/archive/v0.8.0.tar.gz -o /var/snap/microk8s/2399/tmp/kube-prometheus/kube-prometheus.tar.gz
[root@server1:actions/]#

```

I did try to manually put the file into `/var/snap/microk8s/2399/tmp/kube-prometheus/kube-prometheus.tar.gz` and then enabling, but that didn’t see to help.

Is there any way to override the URL it pulls from or other way to manually install prometheus in an air-gapped scenario?

---

<div class="post-metadata">

**Author:** ![balchua1](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/balchua1/32/5372_2.png) [@balchua1](https://discuss.kubernetes.io/u/balchua1)\
**Post date:** [August 24, 2021, 1:39pm UTC](https://discuss.kubernetes.io/t/configuring-github-url-when-enabling-add-ons/17184/2 "2021-08-24T13:39:35Z")

</div>

Right now, there’s no way to do that.  
The addons are there to easily add them into the cluster. If the version that comes with the addon doesn’t fit your need, you can go to the upstream repo.

---

<div class="post-metadata">

**Author:** ![flipcode](https://avatars.discourse-cdn.com/v4/letter/f/848f3c/32.png) [@flipcode](https://discuss.kubernetes.io/u/flipcode)\
**Post date:** [August 25, 2021, 7:43am UTC](https://discuss.kubernetes.io/t/configuring-github-url-when-enabling-add-ons/17184/3 "2021-08-25T07:43:58Z")

</div>

I managed to figure out that manually pre downloading and manually running the install steps in the enable script (tar, mv) and finally running the `microk8s enable` step again manages to enable this.
