[Starlingx-discuss] config_controller fails because of kubernetes

[Marcel Schaible]

Thanks Curtis!

Since there was no configuration option for setting up the internet access I suspect I have to do this manually before running the config_controller?

Is this somewhere in the installation docs mentioned?






> Curtis <serverascode at gmail.com> hat am 21. März 2019 um 17:14 geschrieben:
> 
> 
> On Thu, Mar 21, 2019 at 11:53 AM Marcel Schaible <
> marcel at schaible-consulting.de> wrote:
> 
> > Hi,
> >
> > I have tried the image from yesterday 20190320 and the config_controller
> > bails out with the
> > following error in the puppet.log:
> >
> > [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.12.3:
> > output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http:
> > request canceled while waiting for connection (Client.Timeout exceeded
> > while awaiting headers)
> >
> > When I try to access the url with another computer ith proper internet
> > access I'll et the response:
> >
> > {"errors":[{"code":"UNAUTHORIZED","message":"Unauthorized access."}]}
> >
> > Is this expected?
> >
> > So does that mean, that I have a working internet connection for
> > installation?
> >
> 
> This is how I understand it, and hopefully someone else will correct me or
> better explain if needed, but basically the ISO does not contain any Docker
> images. But when running config_controller, it needs to have Docker images
> to deploy Kubernetes. So those Docker images have to come from somewhere.
> So to answer your question, yes, you do need an internet connection at some
> point to get the Docker images.
> 
> There is the option to 1) use a Docker proxy or 2) use a local Docker
> registry as an "alternative registry", ie. offline or "air gapped." Though
> I'm there may be a bug in option #2, and option #1 still requires that the
> proxy has access to the images somehow (generally the proxy is used as a
> cache, and the proxy itself still has access to the internet).
> 
> 
> >
> > Since I don't want to use kubernetes/docker at the moment, how can I
> > disable this behavior?
> >
> >
> Basically, I don't think it's possible to have StarlingX without
> Kubernetes...it's not an option any more. That's a major design decision
> the project has made and in many ways is a key feature of StarlingX. I
> don't think you would want to avoid it even if it were possible. :)
> 
> Thanks,
> Curtis
> 
> 
> 
> > Thanks
> >
> > Marcel
> >
> > _______________________________________________
> > Starlingx-discuss mailing list
> > Starlingx-discuss at lists.starlingx.io
> > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
> >
> 
> 
> -- 
> Blog: serverascode.com