Re: Unable to dynamically provision cinder volumes

Got some help on the #sig-openstack channel in kubernetes from @fengyunpan Turns out I needed to add [BlockStorage] bs-version=v2 to /etc/origin/cloudprovider/openstack.conf It looks like better autodetection exists in Kubernetes 1.7

Re: Origin router and X-Forwarded-For

Hi Marcello. on Montag, 16. Oktober 2017 at 15:23 was written: > Hi, > I have tried it and it worked fine but the problem is override the > default wildcard certificate and configure a different certificate, > because it's not possible to configure the intermediate CA chain into > the admin

Re: Web console overview sections?

Tako, anything with an `app` label is shown as an application. If you add an app label to your deployment config or pods, they should show up on the overview as an application with that name. On Mon, Oct 16, 2017 at 12:47 PM, Tako Schotanus wrote: > Hi, > > I just updated

Web console overview sections?

Hi, I just updated my minishift installation (from 1.1 to 1.7) and the web console overview page has changed again. A .yaml template that I was using before to create our services (5 pods) now puts the app's main entry point in the list of "Other Resources" while a seemingly random pod has been

Re: Possible to use AWS elasitcsearch for OpenShift logging?

You can configure fluentd to forward logs (see https://docs.openshift.com/container-platform/latest/install_config/aggregate_logging.html#sending-logs-to-an-external-elasticsearch-instance). Note the caveat, "If you are not using the provided Kibana and Elasticsearch images, you will not have the

Re: Origin router and X-Forwarded-For

Hi, I have tried it and it worked fine but the problem is override the default wildcard certificate and configure a different certificate, because it's not possible to configure the intermediate CA chain into the admin panel. I tried to configure the CA cert with the root CA and the subordinate CA

Draining in Rolling Upgrade

Hi Everyone, In OCP 3.5, suppose we have 3 or multiple instances in a cluster for version 1.0 and there is a newer version 1.1, but we need these services drain and updated 1 by 1. How can we adjust it in deployment YML? Could you please guide me a reference document? Thanks in advance. And

Re: 2 clusters with the same internal ip addresses

Hi Lionel yes these IPs are not exposed to the outside (S-NAT with the node IP address). If you are not calling external services with conflicting IP addresses you are fine. Regards, Frédéric On Mon, Oct 16, 2017 at 11:40 AM, Lionel Orellana wrote: > Hi, > > > Can two

2 clusters with the same internal ip addresses

Hi, Can two different clusters use the same ip ranges for osm_cluster_network_cidr and openshift_portal_net? Those ip’s are all internal so should be ok? I'm trying to save the hassle of reserving two more ranges for my second cluster. I don't want/need them to know about each other. Thanks