[Starlingx-discuss] [Containers] How to retrieve data from a helm chart already applied
Yong Hu
yong.hu at intel.com
Wed Jul 31 21:51:28 UTC 2019
Have a try with setting NO_PROXY env:
export NO_PROXY="10.*, *.intel.com, localhost, 127.0.0.1,192.168.206.2"
On 31/07/2019 1:07 PM, Perez Carranza, Jose wrote:
> Hi
>
> I’m trying to inspect a chart already applied on the StarlignX
> deployment, does anyone knows if I’m missing something on the steps
> mentioned below, because currently I’m not able to retrieve the data.
>
> controller-0:~$ helm list |grep nova
>
> osh-openstack-nova 1 Thu Jul 18
> 19:32:41 2019 DEPLOYED nova-0.1.0
> openstack
>
> osh-openstack-nova-api-proxy 1 Thu Jul 18
> 19:32:41 2019 DEPLOYED nova-api-proxy-0.1.0
> openstack
>
> -------
>
> controller-0:~$ helm repo update
>
> Hang tight while we grab the latest from your chart repositories...
>
> ...Skip local chart repository
>
> ...Unable to get an update from the "starlingx" chart repository
> (http://127.0.0.1:8080/helm_charts/starlingx):
>
> Get
> http://127.0.0.1:8080/helm_charts/starlingx/index.yaml: dial tcp
> 127.0.0.1:8080: connect: connection refused
>
> ...Unable to get an update from the "stx-platform" chart repository
> (http://127.0.0.1:8080/helm_charts/stx-platform):
>
> Get
> http://127.0.0.1:8080/helm_charts/stx-platform/index.yaml: dial tcp
> 127.0.0.1:8080: connect: connection refused
>
> ...Unable to get an update from the "stable" chart repository
> (https://kubernetes-charts.storage.googleapis.com):
>
> Get
> https://kubernetes-charts.storage.googleapis.com/index.yaml: dial tcp
> 172.217.164.112:443: connect: connection timed out
>
> Update Complete. ⎈Happy Helming!⎈
>
> controller-0:~$ helm inspect osh-openstack-nova
>
> Error: failed to download "osh-openstack-nova" (hint: running `helm repo
> update` may help)
>
> Regards
>
> Jose
>
> --
>
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
>
More information about the Starlingx-discuss
mailing list