Will do that.
Still i think this should be handled by the playbooks given that I
specifically disable internal registry and specify the oreg_url.
Thanks for your help Adam & Ben
best
Chris
On Mon, Aug 13, 2018 at 5:46 PM Adam Kaplan wrote:
> Those errors make sense, then. You can create a new
Those errors make sense, then. You can create a new
ImageStream+ImageStreamTag that points to the rhscl nodejs images, and
reference that in the build.
On Mon, Aug 13, 2018 at 10:26 AM Sandrini, Christian <
christian.sandr...@bis.org> wrote:
> Something interesting. The buildconfig tries to pull
Something interesting. The buildconfig tries to pull from (…/openshift/nodejs)
nexus.bisinfo.org:8500/openshift/nodejs@sha256:7b26a9d8ace47e939a9fcdca61620dbe47d1b936e68983e252cca50991704c7c
This does not exist in nexus
# docker pull nexus.bisinfo.org:8500/openshift/nodejs:latest
Trying to pull
Thanks David. It worked!
So is openshiftwebconsoleconfigs.webconsole.operator.openshift.io a
resource defined specifically using Operator?
The documentation
https://docs.okd.io/3.10/install_config/web_console_customization.html#loading-custom-scripts-and-stylesheets
needs to be updated to re
Hi Ben
No authentication is required.
Best
Chris
From: Ben Parees [mailto:bpar...@redhat.com]
Sent: 13 August 2018 15:44
To: Sandrini, Christian
Cc: Adam Kaplan ; users@lists.openshift.redhat.com
Subject: Re: Using an external registry for the cluster
On Mon, Aug 13, 2018 at 9:32 AM, Sandrin
On Mon, Aug 13, 2018 at 9:32 AM, Sandrini, Christian <
christian.sandr...@bis.org> wrote:
> Hi Adam
>
>
>
> Yes. I can actually manually pull it from nexus on any openshift node.
> Because we use an internally signed certificate I was wondering if it might
> have something to do it with?
>
you'd
Hi Adam
Yes. I can actually manually pull it from nexus on any openshift node. Because
we use an internally signed certificate I was wondering if it might have
something to do it with? The node is able to pull because I put the
certificates into /etc/pki. Not sure the builder image has that inf
Hello.
I am trying to install an Openshift 3.10 Origin in AWS.
I am having an issue with hostnames, in the sense that after running the
install playbooks from openshift ansible repo, the cluster is set up using
internal AWS DNS as hostnames.
But during the install the playbooks looks for pods using
Have you pushed the nodejs s2i image to your nexus registry? The ansible
playbook does not do this for you.
If you haven't done so, you can manually pull the nodejs s2i image from
registry.access.redhat.com, then push it to the nexus registry.
On Mon, Aug 13, 2018 at 9:16 AM Sandrini, Christian <
Hi Adam
This is the buildconfig
# oc get buildconfig test -o yaml
apiVersion: build.openshift.io/v1
kind: BuildConfig
metadata:
annotations:
openshift.io/generated-by: OpenShiftWebConsole
creationTimestamp: 2018-08-10T11:30:11Z
labels:
app: test
name: test
namespace: test
reso
Feature! :)
Because it is operator managed, you need to edit the config leading to the
operator. Try `oc edit
openshiftwebconsoleconfigs.webconsole.operator.openshift.io` and update the
spec.config to what you need.
On Sat, Aug 11, 2018 at 3:54 AM Ahmed Ossama wrote:
> Hi Everyone,
>
> I am ru
Hi Chris,
I'm with the developer experience team - can you please provide a snippet
of the build config that is breaking? We'd like to see which image streams
are being used in the build.
Thank You,
Adam
On Wed, Aug 8, 2018 at 2:58 AM Sandrini, Christian <
christian.sandr...@bis.org> wrote:
> H
12 matches
Mail list logo
