Hi.
@Fabio: When you use the advanced setup you should set the
`openshift_master_cluster_public_hostname` to `hosting.wfp.org`and rerun
the install playbook.
I suggest to take a look into the now very detailed documentation.
It’s also worth mentioning that the console is not haproxy. That is the
router, which run on the infrastructure nodes. The console/api server runs
something else.
On Wed, 3 Jan 2018 at 1:46 am, Fabio Martinelli <
fabio.martinelli.1...@gmail.com> wrote:
> It was actually needed to rewrite the
Looks like this problem has fixed itself over the last couple of weeks
(I just updated openshift-ansible on the release-3.7 branch) .
That package dependency error is no longer happening.
It now seems possible to deploy a minimal 3.7 distribution using the
Ansible installer.
I have no idea
Have a look at [1] which should explain how to connect the IS with the
secret. Additionally,
there's [2] which explains problems when auth is delegated to a different
uri.
Maciej
[1]
https://docs.openshift.org/latest/dev_guide/managing_images.html#private-registries
[2]
Hi all,
I’m successfully using a DeploymentConfig (DC) and an ImagePullSecret (IPS)
templates with OpenShift Origin v3.6 to spin-up my application from a container
image hosted on a private GitLab registry. But I want the deployment to
re-deploy when the GitLab image changes and to do this I
