Question about the IKO topology

Question

Joost Platenburg · Mar 21, 2022

#Kubernetes #InterSystems IRIS for Health

Hi,

Are we correct to assume that the IKO topology only allows for the use of one 'data' node type, and one 'compute' node type? So if we want to use several different iris based compute nodes (or data nodes) we have to apply several yaml files? So the following topology config is not possible:

topology:
data:
image: dvza.healthexchange.nl/mmres:0.1
data:
image: dvza.healthexchange.nl/mmauth:0.1
data:
image: dvza.healthexchange.nl/somethingelsethatisbasedonirisimage:0.1

Thanks in advance.

Product version: IRIS 2021.2

$ZV: iris:2021.2.0.651.0

Discussion (1)1

Bob Kuszewski · Mar 23, 2022

Yes, IKO provided support for a simple IRIS topology where all Compute (ECP clients) nodes are the same, as are all data (shards), and all web gateways.

IKO is a tool that simplifies common deployments of IRIS in Kubernetes. It takes your description of your irisCluster and creates the base kubernetes objects needed to support that deployment (a real lifesaver for sharding/mirroring deployments). You can always see what IKO created and use that as inspiration for creating your own YAML to deploy IRIS in your kubernetes environment.

0 0