I see, so for point 1 I cannot help much. It worked well for me. For the second point, do kubernetes manifests exist for esr and esr gui? You need the deployment and the service kubernetes manifests as explained in my previous mail.
Thanks, Alexis > On Dec 6, 2017, at 10:57 AM, Gaurav Gupta (c) <guptagau...@vmware.com> wrote: > > thanks Alexis > > response in line . > > with best regards > gaurav > From: Alexis de Talhouët <adetalhoue...@gmail.com > <mailto:adetalhoue...@gmail.com>> > Sent: 06 December 2017 19:57 > To: Gaurav Gupta (c) > Cc: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org>; Michael > O'Brien; Ramesh Tammana; Ramki Krishnan; Arun Arora (c) > Subject: Re: Issues with Kubectl setup and newly pulled dockers not showing > in kubectl list ---namespace > > Hi, > > Some answers inline. > > Thanks, > Alexis > >> On Dec 6, 2017, at 8:34 AM, Gaurav Gupta (c) <guptagau...@vmware.com >> <mailto:guptagau...@vmware.com>> wrote: >> >> Hi All , Michal , Alexis >> >> We are into 2 very distinct issues while trying vDNS Demo on OOM . >> >> issue 1 - kubectl >> post following below information . >> 1. curl -LO >> https://storage.googleapis.com/kubernetes-release/release/v1.7.0/bin/linux/amd64/kubectl >> >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__storage.googleapis.com_kubernetes-2Drelease_release_v1.7.0_bin_linux_amd64_kubectl&d=DwMFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=sMfOd3IsgFDEQjC8M-dExvTijIpkq549dAV5SUgIXqA&s=U5DyMgpJ6JviFTgJx26Y47cLxgUN47vVnIn0wQINhtw&e=> >> 2. chmod +x ./kubectl >> 3. mv kubectl /usr/local/bin >> 4 setting up config in ~/.kube/config >> >> 5. while running kubectl cluster-info an dump >> >> oot@k8s-node-0-30a414d1-5a13-41a5-a15a-5970f7fb74ed:~/.kube# kubectl >> cluster-info dump >> Unable to connect to the server: dial tcp 10.110.208.207:443: i/o timeout >> >> root@k8s-node-0-30a414d1-5a13-41a5-a15a-5970f7fb74ed:~/.kube# kubectl >> cluster-info >> Kubernetes master is running at https://10.110.208.207:443/ >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__10.110.208.207-3A443_&d=DwMFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=sMfOd3IsgFDEQjC8M-dExvTijIpkq549dAV5SUgIXqA&s=J_jRQV7D3-6OX_JlBX4KkAVZGq0KIka2-kSq-bZfJlw&e=> > AdT: I’m not sure to understand the issue been raised here. Can you clarify? > > [Gaurav ] - I think I have some issues with kubectl setup so if some one > has attempted the kubectl installation and faced similar issues and resolved > them , It will help me as well . > This is needed so that OOM based deployment can be done and health check > scripts refers to kubectl commands . >> >> >> issue 2 - We pulled 2 esr dockers manually inside our OOM deployment . >> However the new dockers are not getting listed in kubectl commands . So, >> essentially these containers dont have any specific IP address attached to >> them along with the port. >> >> questions >> - Are we missing something - I mean is this even valid >> operation in OOM ? . > > AdT: Pulling docker images and starting them will not make them appear in > Kubernetes UI. For that, you need to create Kubernetes manifests defining the > deployment, e.g. how the docker container should looks like (port, > entrypoint, volume, pre-conditions, …) and the service, exposing the ports > defined in the deployment to the external world (when using NodePort). > > [Gaurav ] - The use case is - we had OOM Deployement done with few dockers , > But we wanted to pull 2 more dockers i.e esr and esr gui . We did pull the > dockers from nexsus repo but we donot see them getting listed in the kubectl > list --namespaces .Due to this we are also assuming that No Port /IP Address > is getting assigned to those . > Can this use work or we have to do a complete OOM Deployment fresh ? . > > >> - is there anything else that we should be doing in >> this situation ? . >> >> thanks in advance >> >> with best regards >> gaurav > >
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
