Re: role bindings incorrect after ose 3.2.0 upgrade

Enterprise-Upgrade-3.1-to-3.2#update-cluster-policies-and-roles > On Wed, Jun 1, 2016 at 12:16 PM, Dale Bewley < d...@bewley.net > wrote: >> After upgrading to OSE 3.2.0 developers can no longer use the source build >> strategy. >> I used the playbook to upgrade and

Re: after native HA install atomic-openshift-master service is not enabled

atomic-openshift-master-api and atomic-openshift-master-controllers. How did > you deploy the registry? Are there any failed pods? > On Sun, Jan 31, 2016 at 4:14 PM, Dale Bewley < d...@bewley.net > wrote: >> I'm provisioning a Native HA OpenShift Enterprise 3.1 cluster using b

Re: best practices for custom S2I STI builder images

ipt was not found by the assemble script. [1] https://github.com/getupcloud/sti-php-extra/blob/master/5.6/Dockerfile > -- > Mateus Caruccio / Master of Puppets > GetupCloud.com - Eliminamos a Gravidade > On Wed, Mar 30, 2016 at 12:44 PM, Dale Bewley < d...@bewley.net > wrote: >&

Re: 404 on path based route

nst your apache service by removing the proxy > (haproxy) out of the mix and > curling the pod/endpoint directly ala: > $ curl -H "Host: hello-flask-dale.os.example.com" http://10.1.7.11:8080/ > static/index.html > HTH > On Tue, Apr 5, 2016 at 10:33 AM, Dale Bewley <

Re: route hostname generation in template

- On Apr 8, 2016, at 2:38 PM, Aleksandar Lazic aleksandar.la...@cloudwerkstatt.com wrote: > Hi Dale. > > I have solved this with the > > https://docs.openshift.org/latest/dev_guide/downward_api.html > Thanks for the tip! Looks like it would not solve the route generation problem,

Re: [Openshift-Ansible] Are there a tip to directly execute "roles/openshift_registry/tasks/main.yml" without execute all "playbooks/byo/config.yml" playbook ?

Deploying the registry by hand is not that tough. https://docs.openshift.com/enterprise/3.1/install_config/install/docker_registry.html But you could construct your own small playbook that calls only the openshift_registry role. - On May 2, 2016, at 2:35 AM, Stéphane Klein

Re: Iptables changes?

- On Mar 23, 2016, at 7:59 AM, Jason DeTiberus wrote: > On Wed, Mar 23, 2016 at 10:30 AM, Fernando Montenegro < > fsmontene...@gmail.com > > wrote: >> Hi, >> (OO 1.1 running on CentOS Atomic) >> How would I go about introducing my own iptables changes, it at all

Re: s2i-base ancestry

t; it convenient, great, but its primary purpose is to serve as a common base for > the existing suite of SCL-based s2i images, its use as a general base for s2i > images is a secondary goal (meaning if it does not serve your purposes, > requests for enhancement will be considered in the context o

ose 3.3 upgrade - metrics deployment mode=refresh error

I'm upgrading from OSE 3.2 to OCP 3.3. During the redeployment (refresh) of metrics, which starts like this: ``` [root@ose-test-master-01 playbook-openshift]# oc new-app -f \ > > /usr/share/openshift/examples/infrastructure-templates/enterprise/metrics-deployer.yaml > \ > -p

audit users of imagestream to enable deprecation

I have created some imagestreams and shared images in my cluster which I would like to deprecate now that they are provided upstream. Does anyone have any tips or tools for uncovering consumers of a particular imagestream or image? I can write something to troll through buildconfigs and

is it recommended to disable ipv6

I am running OCP 3.7.54. I can only find notes indicating IPv6 is not supported, but no indication in the prereqs that it should be disabled on the nodes. In my case IPv6 is not specifically configured so there are only link local addresses present. I suspect it is causing me problems. While

etcd v2 data after upgrade from 3.6 to 3.7

I'm on RHEL, OCP 3.9.60. In anticipation of upgrading to 3.10 I am trying to determine if the v2 data I can see remaining in etcd is still relevant or if I can abandon it. Given this step https://docs.openshift.com/container-platform/3.7/upgrading/migrating_etcd.html was executed

Re: Changing master-config.yaml through Ansible hosts file or directly?

, and upgrades would wipe out your customizations until you reapply them. -- Dale Bewley > On Feb 11, 2019, at 04:31, mabi wrote: > > Hello, > > I installed okd 3.12 using the Ansible playbook deploy_cluster.yml and now I > was having the following questions regarding con

Re: Which DNS to use?

$openshift_master_default_subdomain would be resolvable to your users in exactly the same way google.com would be. It’s a real domain. It’s not OpenShift specific. You will manage this domain in your enterprise per usual, and create wildcard DNS A records for the subdomain which return the IPs of

Re: how to supply ca trust bundle to bootstrap ignition config for openstack

rom commit 2355d9b2dd662c0043133d76273c5cf10e0ce00a release image quay.io/openshift-release-dev/ocp-release-nightly@sha256:3828e79b24b1891b9bec8b47fb7bf2fe093d7211dc9687cff317f475fa15f999 On Wed, Nov 20, 2019 at 9:38 AM Dale Bewley wrote: > After this merge I understand I can supply a CA bundle to enable ignition > to trust my

Re: how to supply ca trust bundle to bootstrap ignition config for openstack

I have figured out that the CA cert needs to go in install-config.yaml at .additionalTrustBundle. On Wed, Nov 20, 2019 at 9:38 PM Dale Bewley wrote: > I believe the ca bundle value should show up here: > > $ cat terraform.openstack.auto.tfvars.json | jq -r > .openstack_bootstrap_s

ocp 4.3 nightly install on openstack queens

Hello, I'm testing OCP 4.3 2019-11-19 nightly on OSP 13. I added my CA cert [1] to install-config.yaml [3] and the installer now progresses. I can even `oc get nodes` and see the masters. [2]. I still have the following errors and no worker nodes though. ERROR Cluster operator authentication

Re: ocp 4.3 nightly install on openstack queens

bug.cgi?id=1769879 and https://github.com/openshift/enhancements/pull/115 and running 3.11 :) On Wed, Dec 4, 2019 at 9:29 PM Joel Pearson wrote: > > > On Wed, 4 Dec 2019 at 08:02, Dale Bewley wrote: > >> >> On Tue, Nov 26, 2019 at 7:29 PM Joel Pearson < >> japear..

Re: ocp 4.3 nightly install on openstack queens

On Tue, Nov 26, 2019 at 7:29 PM Joel Pearson wrote: Thanks for taking the time to reply, Joel. > On Sat, 23 Nov 2019 at 13:21, Dale Bewley wrote: > >> Hello, >> I'm testing OCP 4.3 2019-11-19 nightly on OSP 13. >> >> I added my CA cert [1] to install-config.y

Re: ocp 4.3 nightly install on openstack queens

On Sat, Dec 14, 2019 at 3:31 AM Joel Pearson wrote: > I think there is one last thing that is worth trying... > > On Sat, 14 Dec 2019 at 18:56, Dale Bewley wrote: > >> Thanks for the tips, Joel, but no luck so far with >> 4.3.0-0.nightly-2019-12-13-180405. >>

Re: ocp 4.3 nightly install on openstack queens

/etc/pki drwxr-xr-x. 6 root root 81 Dec 14 07:17 /etc/pki sh-4.2$ curl https://openstack.domain.com:13000 curl: (77) Problem with the SSL CA cert (path? access rights?) On Sun, Dec 15, 2019 at 7:52 PM Joel Pearson wrote: > > > On Mon, 16 Dec 2019 at 14:41, Dale Bewley wrote: > >

access to nightly OCP builds

I'm thwarted from installing OCP 4.2 on OSP 13 due to lack of support for a typical enterprise TLS config [1]. It is preventing the bootstrap node from reaching Swift due to "self-signed" cert. I see that may be mostly fixed upstream [2] now. If this fix is in a nightly build [3] of OCP 4.3, how

how to supply ca trust bundle to bootstrap ignition config for openstack

After this merge I understand I can supply a CA bundle to enable ignition to trust my OpenStack Swift endpoint https://github.com/openshift/installer/pull/2587/files#diff-8f7812d0db7f9cf17958b3a70170f7a0 I am trying with the openshift-install-mac-4.3.0-0.nightly-2019-11-19-053808.tar.gz build.