3:16 p.m.
Summers I circumvented the problem here. Seems the application doesn't like
my ingress:
/ingress.yaml
kind: Ingress
apiVersion: extensions/v1beta1
metadata:
annotations:
ingress.kubernetes.io/whitelist-source-range: 10.0.0.0/8,127.0.0.1/32
ingress.kubernetes.io/proxy-body-size: 1m
ingress.kubernetes.io/rewrite-target: /
ingress.kubernetes.io/ssl-redirect: "true"
name: aerogear
namespace: blah-v
spec:
rules:
- host:myhost.com
http:
paths:
- backend:
serviceName: aerogear
servicePort: 8080
path: /
tls:
- hosts:
- myhost.com/
I've ran the same image same databases without this ingress pointing a dns
directly to it. And it works. So now we know where is the problem still I
cannot grasp its reason.
Summers Pittman wrote
On Wed, Jul 5, 2017 at 8:35 AM, Summers Pittman <
supittma@
> wrote:
>
>
> On Mon, Jul 3, 2017 at 2:17 PM, vfbsilva <
vfbsilva@
> wrote:
>
>> Summers, seems I was missing:
>>
>> /./bin/ups-migrator update/
>>
>> It was not clear from me when building the image I needed to perform
>> this
>> step. Now I'm facing some SSL miss configuration, whenever I try to
>> acess
>> /ag-push/ or /auth I get an SSL error:
>>
>> /Exception handling request to /ag-push/: java.lang.RuntimeException:
>> Unable
>> to resolve realm public key remotely/
>>
>>
>> the image ships with self-signed certs under:
>>
>> *standalone/configuration/certs/*
>>
>> I've ran certificate.sh providing my domain name and adding it to
>> standalone.xml still seems it is not importing my key. What am I
>> missing?
>>
>>
>>
> Looping back in for posterity :
>
> The ag-auth deployment isn't running in Kubernetes for some reason. The
> error you are getting is from the auth system not deploying not from SSL.
> The realm public key is a configuration option there. I've created
> https://issues.jboss.org/browse/AEROGEAR-1747 with more details. However
> that issue may never get fixed because we are splitting up auth from the
> deployed package "soon". Since auth will be deployed separately the
> problem just won't exist any more.
>
>
So it looks like resetting my mySQL databases solved the problem I was
having and UPS deployed normally in kubernetes. I also switched to the
aerogear/unifiedpush-wildfly-dev image which may or may not have affected
the result as well.
> Summers
>
>
>>
>>
>>
>> --
>> View this message in context: http://aerogear-users.1116366.
>> n5.nabble.com/Aerogear-users-Problems-deplying-aerogear-in-k
>> ubernetes-with-wildfly-eap-tp1132p1135.html
>> Sent from the aerogear-users mailing list archive at Nabble.com.
>> _______________________________________________
>> Aerogear-users mailing list
>>
Aerogear-users@.jboss
>>>
>
>
_______________________________________________
Aerogear-users mailing list
Aerogear-users@.jboss
--
View this message in context:
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Problems-deply...
Sent from the aerogear-users mailing list archive at Nabble.com.