Is wireguard setup done?
Are you connected to wireguard?
Also all the loadbalancer configuration relevant to this is performed?
loadbalancer configuration
yes wireguard setup is done , I am connected to wireguard aswell and also loadbalancer configuration has been performed. I am setting it up in gcp just wanted you to take a note of that.
Please can someone revert , a bit quicker on this matter @syed.salman @keshavs @ckm007 @HarikrishnaReddy
Hi @Arjun_Bose ,
Yes, one of of the SMEs will respond here, team has been a bit occupied, have requested them.
Best Regards
Team MOSIP
Its been 2 days no one reached out yet. @keshavs
please can someoe help on this ,
when i try to access the prereg ui , i am getting this
Dear @Arjun_Bose ,
Apologies for the delay, we are to look into the aspect when load balancer has been used and solution for the same. One of our colleagues is looking into this and will be responding here with inputs. Kindly bear with us this while.
Best Regards
Team MOSIP
Please look into the prereg issue first , its also unable to find this https://prereg.sandbox.radiant-mosip.org/preregistration/v1/login/config
please can anyone respond to the issue @keshavs @syed.salman @HarikrishnaReddy
Hi @Arjun_Bose
Apologies for the delay from our side as I see you haven’t got a reply back from our side let me assign it to one of my team members asap who can look into this and help you out.
Best regards,
Team MOSIP
Hi @Arjun_Bose
The URL for PreReg services seems incorrect. It has one extra slash.
That is why you are getting 404 err.
Hope this helps!
have resolved this but still getting error PreRegistration
https://prereg.sandbox.radiant-mosip.org/pre-registration-ui/#/
Could you please provide the load-balancer configuration and istio nodeport configuration?
You can get the istio configuration via the below command
kubectl -n istio-system get iop istio-operators-mosip -o yaml
im not using istio i have exposed it using a public loadbalancer and an ingress. I have set it up in gke so have done so as I was facing issues with istio.
this is the prereg-ui service cluster ip
apiVersion: v1
kind: Service
metadata:
annotations:
cloud.google.com/neg: ‘{“ingress”:true}’
cloud.google.com/neg-status: ‘{“network_endpoint_groups”:{“80”:“k8s1-092b4e2b-prereg-prereg-ui-80-ebae32bc”},“zones”:[“us-central1-a”,“us-central1-b”,“us-central1-c”,“us-central1-f”]}’
meta.helm.sh/release-name: prereg-ui
meta.helm.sh/release-namespace: prereg
creationTimestamp: “2024-07-29T08:53:23Z”
labels:
app.kubernetes.io/component: mosip
app.kubernetes.io/instance: prereg-ui
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: prereg-ui
helm.sh/chart: prereg-ui-12.0.1-B2
managedFields:
- apiVersion: v1
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.: {}
f:meta.helm.sh/release-name: {}
f:meta.helm.sh/release-namespace: {}
f:labels:
.: {}
f:app.kubernetes.io/component: {}
f:app.kubernetes.io/instance: {}
f:app.kubernetes.io/managed-by: {}
f:app.kubernetes.io/name: {}
f:helm.sh/chart: {}
f:spec:
f:internalTrafficPolicy: {}
f:ports:
.: {}
k:{“port”:80,“protocol”:“TCP”}:
.: {}
f:port: {}
f:protocol: {}
f:selector: {}
f:sessionAffinity: {}
f:type: {}
manager: helm
operation: Update
time: “2024-07-29T08:53:23Z” - apiVersion: v1
fieldsType: FieldsV1
fieldsV1:
f:spec:
f:ports:
k:{“port”:80,“protocol”:“TCP”}:
f:targetPort: {}
manager: unknown
operation: Update
time: “2024-08-06T16:04:58Z” - apiVersion: v1
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
f:cloud.google.com/neg-status: {}
manager: glbc
operation: Update
subresource: status
time: “2024-08-08T18:43:55Z”
name: prereg-ui
namespace: prereg
resourceVersion: “10341816”
uid: 11b7fbbf-36d0-4449-8cce-24e2918540c9
spec:
clusterIP: 10.137.246.121
clusterIPs: - 10.137.246.121
internalTrafficPolicy: Cluster
ipFamilies: - IPv4
ipFamilyPolicy: SingleStack
ports: - port: 80
protocol: TCP
targetPort: 8080
selector:
app.kubernetes.io/instance: prereg-ui
app.kubernetes.io/name: prereg-ui
sessionAffinity: None
type: ClusterIP
status:
loadBalancer: {}
and this is the ingress
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
annotations:
ingress.kubernetes.io/backends: ‘{“k8s1-092b4e2b-kube-system-default-http-backend-80-ec2f7a65”:“HEALTHY”,“k8s1-092b4e2b-prereg-prereg-ui-80-ebae32bc”:“HEALTHY”}’
ingress.kubernetes.io/forwarding-rule: k8s2-fr-7u3htvsg-prereg-prereg-ui-ingress-fc63507h
ingress.kubernetes.io/target-proxy: k8s2-tp-7u3htvsg-prereg-prereg-ui-ingress-fc63507h
ingress.kubernetes.io/url-map: k8s2-um-7u3htvsg-prereg-prereg-ui-ingress-fc63507h
kubectl.kubernetes.io/last-applied-configuration: |
{“apiVersion”:“networking.k8s.io/v1",“kind”:“Ingress”,“metadata”:{“annotations”:{“nginx.ingress.kubernetes.io/rewrite-target”:“/”},“name”:“prereg-ui-ingress”,“namespace”:“prereg”},“spec”:{“rules”:[{“host”:“prereg.sandbox.radiant-mosip.org”,“http”:{“paths”:[{“backend”:{“service”:{“name”:“prereg-ui”,“port”:{“number”:80}}},“path”:“/pre-registration-ui/”,“pathType”:"Prefix”}]}}]}}
nginx.ingress.kubernetes.io/rewrite-target: /
creationTimestamp: “2024-08-08T18:43:55Z”
finalizers:
- networking.gke.io/ingress-finalizer-V2
generation: 6
managedFields: - apiVersion: networking.k8s.io/v1
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.: {}
f:kubectl.kubernetes.io/last-applied-configuration: {}
f:nginx.ingress.kubernetes.io/rewrite-target: {}
manager: kubectl-client-side-apply
operation: Update
time: “2024-08-08T18:43:55Z” - apiVersion: networking.k8s.io/v1
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
f:ingress.kubernetes.io/backends: {}
f:ingress.kubernetes.io/forwarding-rule: {}
f:ingress.kubernetes.io/target-proxy: {}
f:ingress.kubernetes.io/url-map: {}
f:finalizers:
.: {}
v:“networking.gke.io/ingress-finalizer-V2”: {}
f:status:
f:loadBalancer:
f:ingress: {}
manager: glbc
operation: Update
subresource: status
time: “2024-08-08T18:47:08Z” - apiVersion: networking.k8s.io/v1
fieldsType: FieldsV1
fieldsV1:
f:spec:
f:rules: {}
manager: unknown
operation: Update
time: “2024-08-09T10:36:29Z”
name: prereg-ui-ingress
namespace: prereg
resourceVersion: “10992808”
uid: f886d06d-7c30-4ee0-b5b4-3bf48eb29cd3
spec:
rules: - host: prereg.sandbox.radiant-mosip.org
http:
paths:- backend:
service:
name: prereg-ui
port:
number: 80
path: /pre-registration-ui/*
pathType: ImplementationSpecific
status:
loadBalancer:
ingress: - ip: 34.120.207.136
- backend:
It appears the issue may be related to the ingress rule. The current path is set as path: /pre-registration-ui/*. Please consider updating it to /. The host (prereg.sandbox.xyz.net) will be validated before routing to the service.
Additionally, could you please share the challenges you encountered during the deployment of Istio?
I am unable to route anything from istio-ingressgateway-internal nor istio-ingressgateway
still not working i tried giving just the /
Could you please provide all the ingress configurations?
1 Like
I have deployed istio v.1.15 , and my gke version is 1.28 (the lowest I can go in gke is 1.27) , i was seeing some documentations of istio which says 1.15 is not compatible with 1.28 gke verson , also when i have installed istio (istiod,istio-ingressgateway and ingressgateway-internal) and using the cname values in the dns for the services to be routed using istio , its not working both for internal and extenal , please can you suggest some way @syed.salman @keshavs
The compatible Istio version is v1.22.0.
Please ensure that you use either Istio or the default Ingress, but not both. If you choose to use the default Ingress, you’ll need to manually create ingress resources for all deployed services.
This is my setup
now when i try to access regclient its taking me to this page
https://regclient.sandbox.radiant-mosip.org/ but i am unable to access it but when i try http://regclient.sandbox.radiant-mosip.org/ , it is accessible