Re: How to improve pod scheduling

The scheduler is configurable. Most likely, your scheduler is configured to use "MostRequestedPriority" (see #1), which tries to put all the pods pods on the smallest number of nodes (so you can shutdown the excess nodes). This priority function is used when running on a cloud provider, where you c

Re: Node not getting taint

You can verify by using oc get nodes/node-dev1 -o yaml You can also try seeing if something is overriding the taint by running: oc adm taint nodes node-dev1 mode=testing:NoSchedule && oc get nodes/node-dev1 -o yaml It's likely you'll see the taint, but it will get removed later. M. On 06. 12

Re: DNS resolving problem - in pod

he node ip -on which the dnsmasq was started. What is strange the pod is obtaining duplicated entries. On node, the /etc/resolv.conf has entries: Obraz w treści 3 The origin node config file has got exactly the same ip address which is the IP of node. Best regards

Re: DNS resolving problem - in pod

1. is the service in the same namespace as the pod you're testing in? 2. connect through the FQDN of the service (kibanasg.fullnamespace.svc.cluster.local) On 20. 10. 2017 11:14, Łukasz Strzelec wrote: Thx guys ;)Nope, this is not this case. I've notice that I can reach SVC via IP addresses.

Re: help with redinessProbe check

Neither of the two forms are correct, because they don't run the command in a shell (and you need one because you're actually running multiple commans & using pipes). The correct form is: readinessProbe: exec: command: - sh - -c

Re: Rolling pod evacuation

help >> you today if you run a single pod. I think those deployments will block >> evacuation and that may be a reason why we didn't enable them for users >> initially. >> >> On Fri, Apr 21, 2017 at 9:27 AM, Marko Lukša >> wrote: >> >>> He isn&

Re: Rolling pod evacuation

He isn't performing a rolling upgrade; he just wants to drain a node one pod at a time. On 21. 04. 2017 09:18, Michail Kargakis wrote: If you used those settings and it wasn't honoured then it's a bug. On Fri, Apr 21, 2017 at 1:38 AM, Andrew Lau > wrote: I

Re: Rolling pod evacuation

Take a look at PodDisruptionBudget. It allows you to specify the minimum number of pods that must be kept running when removing pods voluntarily (draining nodes is an example of this). But this feature may not be in OpenShift yet (IIRC draining nodes in Kubernetes honors the PodDisruptionBudget

Re: setting up routes

10 msec ;; SERVER: 192.168.178.1#53(192.168.178.1) ;; WHEN: Tue Mar 21 06:35:19 2017 ;; MSG SIZE rcvd: 83 I am not sure if minishift exposes the ability to easily override the public hostname that apps are made available when first starting it up. Graham On 21 Mar 2017, at 6:23 AM, Marko Lukš

Re: setting up routes

Actually, parksmap-katacoda-my-project.192.168.64.18.xip.io gets resolved to 192.168.64.18. If that's the IP of your minishift VM and the OpenShift router is running and accepting connections on port 80, you should be able to access your service through that URL. On 20. 03. 2017 16:56, Tim Du

Re: default resource requests are not being set on containers

Here's why it happens: If a container has resource limits defined (and doesn't define any requests), then the requests default to the limits. The values are copied from the limits to the requests before the values from the LimitRange are applied to the pod. Because resource requests on the cont

Re: Pod unable to connect with service IP

ot;, "/apis", "/controllers", "/healthz", "/healthz/ping", "/healthz/ready", "/metrics", "/oapi", "/oapi/v1", "/swaggerapi/" ] Thanks Vignesh On Wed, Mar 8, 2017 at 2:

Re: Pod unable to connect with service IP

tput. http://pastebin.com/w2Led1vc Thanks Vignesh On Wed, Mar 8, 2017 at 11:34 AM, Marko Lukša <mailto:marko.lu...@gmail.com>> wrote: Is this the whole output? Some rows seem to be missing. On 08. 03. 2017 16:29, Vignesh M.P.N. wrote: Yes your summary is correct. I have Openshif

Re: Pod unable to connect with service IP

/* cbcluster/couchbase-cluster:http-ui loadbalancer IP */ tcp dpt:jamlink Thanks Vignesh On Wed, Mar 8, 2017 at 9:58 AM, Marko Lukša <mailto:marko.lu...@gmail.com>> wrote: OK, to summarize: - from inside the worker pod, you are able to connect to the master pod through i

Re: Pod unable to connect with service IP

OK, to summarize: - from inside the worker pod, you are able to connect to the master pod through its IP. - the endpoints object shows that the pod is in fact an endpoint of the service - from inside the worker pod, you are not able to connect to the service IP. Is that correct? If yes, pleas

Re: Pod unable to connect with service IP

P address. Any help is much appreciated. Thanks Vignesh On Mon, Mar 6, 2017 at 6:54 AM, Marko Lukša <mailto:marko.lu...@gmail.com>> wrote: On 06. 03. 2017 12:04, Vignesh M.P.N. wrote: Is there any alternative approach on how I could refer to an existing service wit

Re: Pod unable to connect with service IP

On 06. 03. 2017 12:04, Vignesh M.P.N. wrote: Is there any alternative approach on how I could refer to an existing service without using it Service IP? If I understood correctly, you're connecting to "couchbase-master-service:8091". You should try connecting to the IP instead of the hostna

Re: Pod unable to connect with service IP

Service IPs are virtual and can't be pinged. When you create a service with a single port, a few iptables rules get added to each cluster node. When processes running inside pods on those nodes try to connect to the service IP and port, the network packet's destination address is changed to th

Re: Liveness probe frequency

Try this: oc explain pod.spec.containers.livenessProbe Look for initialDelaySeconds and periodSeconds. M. On 07. 12. 2016 11:12, Sobkowiak Krzysztof wrote: Hi Is it possible to set the frequency the liveness/readiness probes are performed? If yes, how can I do it in OpenShift? Kindly reg

Re: JBoss cluster

Hi, so clustering is working, but you still see the warning in the log? If so, we'd like to fix this. I'm assuming you're setting the HTTP_PROXY environment variable? As you've pointed out, since we're calling curl without --no-proxy, it can't access the API server. The actual kube-ping code

Re: Error: valueFrom fieldRef resource => ...env[5].valueFrom.fieldRef.fieldPath: Required value

Your version of oc is too old. Your file works for me, when I use 1.3.0+, but I get the same error as you when using 1.2.0. On 08. 11. 2016 16:22, Stéphane Klein wrote: > This error occurs when you specify multiple field references simultaneously like fieldRef and resourceFieldRef together. I