On Mon, 18 Nov 2019 at 13:05, Clayton Coleman wrote:
> Raise a bug to the installler component, yes
>
Ok thanks, I raised a bug here:
https://bugzilla.redhat.com/show_bug.cgi?id=1773419
> On Nov 17, 2019, at 6:03 PM, Joel Pearson
> wrote:
>
> On Mon, 18 Nov 2019 at 12:37, Ben Parees wrote:
So, I'm running OpenShift 4.2 on Azure UPI following this blog article:
https://blog.openshift.com/openshift-4-1-upi-environment-deployment-on-microsoft-azure-cloud/
with
a few customisations on the terraform side.
One of the main differences it seems, is how the router/ingress is handled.
Normal
Hi,
>> You are however able to login from the console/dashboard?
> The console, for me, isn't at the hostname you mentioned.
The question was about resolving addresses and if the console login works
at all.
As it seems `oc` works when connecting to the API endpoint, right?
> able to login <...>
Gerard,
The console, for me, isn't at the hostname you mentioned. What you've
specified is my api server hostname.
[zaphod@oc6010654212 ~]$ oc get route --all-namespaces | grep console
openshift-console console
console-openshift-console.apps-crc.testing console
Hi,
not sure why this wouldn't work. You are however able to login from the
console/dashboard?
(To make sure the hostname gets resolved; api.crc.testing)
Since CRC is a full OpenShift 4.x installation without specific
configuration, it would behave the same as any other OpenShift 4.x install.
Raise a bug to the installler component, yes
On Nov 17, 2019, at 6:03 PM, Joel Pearson
wrote:
On Mon, 18 Nov 2019 at 12:37, Ben Parees wrote:
>
>
> On Sun, Nov 17, 2019 at 7:24 PM Joel Pearson <
> japear...@agiledigital.com.au> wrote:
>
>>
>>
>> On Wed, 13 Nov 2019 at 02:43, Ben Parees
On Mon, 18 Nov 2019 at 12:37, Ben Parees wrote:
>
>
> On Sun, Nov 17, 2019 at 7:24 PM Joel Pearson <
> japear...@agiledigital.com.au> wrote:
>
>>
>>
>> On Wed, 13 Nov 2019 at 02:43, Ben Parees wrote:
>>
>>>
>>>
>>> On Mon, Nov 11, 2019 at 11:27 PM Ben Parees wrote:
>>>
On Mon,
On Sun, Nov 17, 2019 at 7:24 PM Joel Pearson
wrote:
>
>
> On Wed, 13 Nov 2019 at 02:43, Ben Parees wrote:
>
>>
>>
>> On Mon, Nov 11, 2019 at 11:27 PM Ben Parees wrote:
>>
>>>
>>>
>>> On Mon, Nov 11, 2019 at 10:47 PM Joel Pearson <
>>> japear...@agiledigital.com.au> wrote:
>>>
On
Hi,
https://docs.openshift.com/container-platform/4.2/networking/configuring-ingress-cluster-traffic/configuring-ingress-cluster-traffic-service-external-ip.html#nw-creating-project-and-service_configuring-ingress-cluster-traffic-service-external-ip
.
Step 4 seems like magic. When I do
Tobias,
I _will_ have access to load balancers if needed, but at the moment, I
need to understand how it works. Assume that I do: what exactly does "proxy
to the internal sftp service" mean? I assume "sftp service" would be the
service that I set up, but which piece is the proxy? I don't see
On Wed, 13 Nov 2019 at 01:34, Ben Parees wrote:
>
>
> On Tue, Nov 12, 2019 at 3:45 AM Joel Pearson <
> japear...@agiledigital.com.au> wrote:
>
>>
>>
>> On Tue, 12 Nov 2019 at 15:37, Ben Parees wrote:
>>
>>>
>>>
>>> On Mon, Nov 11, 2019 at 11:26 PM Joel Pearson <
>>>
Hi!
I assume you don't have easy access to load balancers, because that
would be easiest. Just proxy to the internal sftp service.
If you don't I have used Nodeport service in the past. You will lose
the nice port 22 though. If you control the node's ssh daemon, you can
also use ProxyJumps.
12 matches
Mail list logo