Re: Pods stuck on Terminating status

Bahhoo, I believe that the namespace will get stuck also. 'Cause it will only be deleted after all of it's objects got deleted. I would try to restart the Masters services before. Regards, Rodrigo Bersa Cloud Consultant, RHCVA, RHCE Red Hat Brasil

Re: Pods stuck on Terminating status

Hi Rodrigo, No PVs are used. One of the pods is a build pod, the other one's a normal pod without storage. I'll try deleting the namespace. I didn't want to do that,since I had running pods in the namespace. Best, Bahho -Orijinal ileti- Kimden: "Rodrigo Bersa"

Cloud provider register/deregister node and labels

We have not found any documentation or any solutions for this issue. We’ve recently upgraded to 3.7 and have had the same issues. Our work around has been to have cloudwatch check logs for anytime a node (or master) is registered and then it add the logging fluentd label . and if it’s a master,

Reverse Proxy using Nginx

Hello, I have a single host OpenShift cluster. Is it possible to install Nginx (run it as a docker image) and route traffic using Nginx? If so, can someone point out the configurations for NO_PROXY and HTTP_PROXY in this case? I dont want any OpenShift instance IP managed by OpenShift. What I

Re: Pods stuck on Terminating status

Which PV types are in use here? --Humble On Fri, Mar 16, 2018 at 8:42 PM, Rodrigo Bersa wrote: > Hi Bahhoo, > > Are you using PVs on the "Terminating" POD? I heard about some issues with > PODs bounded to PV/PVCs provided by dynamic storage, where you have to > first remove

Re: Pods stuck on Terminating status

Hi Bahhoo, Are you using PVs on the "Terminating" POD? I heard about some issues with PODs bounded to PV/PVCs provided by dynamic storage, where you have to first remove the volume form POD, then the PVPVC. Just after that remove the POD or the DeplymentConfig. If it's not the case, maybe