How to Connect to the Web Gateway Sidecar and Utilize 'seed: path' in IKO 3.6
I am currently using IKO 3.6 to deploy an irisCluster on EKS, but I am facing some challenges. Firstly, I need assistance in understanding how to connect to the Web Gateway sidecar. If anyone has experience with this, I would greatly appreciate any guidance or advice you can offer. Secondly, I am trying to utilize the 'seed: path' options of irisDatabases, but I am unsure of the best approach. If anyone has successfully implemented this feature, I would love to hear about your approach and any insights you can provide. Thank you in advance for any help you can offer!
Comments
Hi Roy,
I can't tell about the "seed: path" but how to play with the Web Gateway sidecar you can follow this example :
https://community.intersystems.com/post/local-k8s-deployment-fhir-server
TL; DR :
In your topology definition :
## deploy webgateway (web server) nodes webgateway: image:k3d-registry.localhost:5000/intersystems/webgateway:2023.1.1.380.0-linux-amd64 type:apache replicas:1 applicationPaths: -/csp/sys -/fhir/r4 alternativeServers:LoadBalancing loginSecret: name:iris-webgateway-secretThe iris-webgateway-secret :
kubectl create secret generic iris-webgateway-secret --from-literal='username=CSPSystem' --from-literal='password=SYS'The config file for iris :
[Actions]ModifyService:Name=%Service_CallIn,Enabled=1,AutheEnabled=16ModifyUser:Name=SuperUser,ChangePassword=0,PasswordHash=a31d24aecc0bfe560a7e45bd913ad27c667dc25a75cbfd358c451bb595b6bd52bd25c82cafaa23ca1dd30b3b4947d12d3bb0ffb2a717df29912b743a281f97c1,0a4c463a2fa1e7542b61aa48800091ab688eb0a14bebf536638f411f5454c9343b9aa6402b4694f0a89b624407a5f43f0a38fc35216bb18aab7dc41ef9f056b1,10000,SHA512ModifyUser:Name=CSPSystem,ChangePassword=0,PasswordHash=a31d24aecc0bfe560a7e45bd913ad27c667dc25a75cbfd358c451bb595b6bd52bd25c82cafaa23ca1dd30b3b4947d12d3bb0ffb2a717df29912b743a281f97c1,0a4c463a2fa1e7542b61aa48800091ab688eb0a14bebf536638f411f5454c9343b9aa6402b4694f0a89b624407a5f43f0a38fc35216bb18aab7dc41ef9f056b1,10000,SHA512To generate PasswordHash :
docker run --rm -it containers.intersystems.com/intersystems/passwordhash:1.1 -algorithm SHA512 -workfactor 10000Add the configmap for iris :
kubectl create cm iriscluster-config --from-file common.cpf the topology of IRIS + Webgateway :
apiVersion:intersystems.com/v1alpha1kind:IrisClustermetadata: name:samplespec:## provide InterSystems IRIS license key if required# licenseKeySecret:# name: iris-key-secret## specify files used to customize the configurations of## InterSystems IRIS nodes, including passwordHash parameter## to set the default password, securing InterSystems IRIS configSource: name:iriscluster-config## topology: defines node types to be deployed; only "data:" is required topology: data: image:k3d-registry.localhost:5000/iris-oauth-fhir-iris:latest## deploy webgateway (web server) nodes webgateway: image:k3d-registry.localhost:5000/intersystems/webgateway:2023.1.1.380.0-linux-amd64 type:apache replicas:1 applicationPaths: -/csp/sys -/fhir/r4 alternativeServers:LoadBalancing loginSecret: name:iris-webgateway-secretThank you for sharing the information. I'm currently facing difficulties in establishing a connection with the sidecar web gateway and I'm uncertain about the process of obtaining the URL for its management portal. Furthermore, I would appreciate guidance on enabling external connections to the Kubernetes network, specifically for the sidecar web gateway.
Try to follow the article, the last part is about the ingress, this will help you to expose the webgateway and have access to the portal.
Right now, I can't help you on specific features of EKS.
Regarding the new topology.data.irisDatabases.seed field, the field is used to let you create databases that start with some starting data in them instead of the usual empty database. This is useful for applications that typically start with some basic information in them. Here's the link to the docs, if they help.
https://docs.intersystems.com/components/csp/docbook/DocBook.UI.Page.cl…