I had deployed this for postgres-init-db
CHART_VERSION=12.0.1-B3
and for postgres it was
helm -n $NS install postgres mosip/postgresql --version 10.16.2 -f values.yaml --wait
@Arjun_Bose may i know which version of mosip you are trying to deploy
v1.20.1-B3 or v1.2.0.1?
v1.20.1-B3 is the one I am trying to deploy.
Config-server is pointing to which branch of config-server.
Is it v1.2.0.1-B3?
Can you please confirm
yes it is pointing towards branch 12.0.1-B3 @syed.salman
I have also mailed you the ida configs.
gitRepo:
uri: GitHub - Alishma/mosip-config
version: radiant-deployment
This is the one being used in config-server.
from which branch the above-mentioned branch radiant-deployment was created?
I think the config branch was created from the 1.2.0.1 branch.
For a workaround, please remove IDA_VCI_EXCHANGE from this line mosip-config/id-authentication-default.properties at f144dffa0f4893f510e3c9bb5397178d4784d086 · Alishma/mosip-config · GitHub
Re-run the ida-keygen
Changing it here would be a bit difficult can i make any changes in the keygenvalue file or the install.sh to refer it as as env variable.
@syed.salman
Then insert the IDA_VCI_EXCHANGE row mentioned in the below image to the IDA DB in the key_policy_def table.
ok let me try that once.
Thanks a ton @syed.salman , this worked.
2 Likes
Dear @Arjun_Bose ,
Glad to hear that the issues are now resolved, @syed.salman thank you for helping out Arjun.
Regards
Team MOSIP
Dear @Arjun_Bose ,
This is to check back on your query and if we can close this now?
Regards
Team MOSIP
I have just one more query I have setup all the services now in MOSIP in gcp , how will i map a domain name to the service for example regclient and
how do i route a domian , for example http://regclient.sandbox.xyz.net to use the (http://api-internal.sandbox.xyz.net/), how can I do this in GCP .
@Arjun_Bose have you used Loadbalancer or nginx in your deployment?
Istio is running as Loadbalancer or Nodeport?
I have deployed istio and its currenctly running as a loadbalancer
please can you revert on this
i am unable to ping the internal lb associated with the istio-ingressgateay-internal also
ping 172.31.47.205
PING 172.31.47.205 (172.31.47.205) 56(84) bytes of data.