#InterSystems Kubernetes Operator (IKO)

Post a job Follow
0 Followers · 35 Posts

The InterSystems Kubernetes Operator (IKO) automates the deployment of InterSystems IRIS® topologies on any Kubernetes platform. It extends the Kubernetes API with the IrisCluster custom resource, which can be deployed as an InterSystems IRIS sharded cluster, distributed cache cluster, or standalone instance (all optionally mirrored) on any Kubernetes platform. The IKO also adds InterSystems IRIS-specific cluster management capabilities to Kubernetes, enabling automation of tasks like adding nodes to a cluster, which you would otherwise have to do manually by interacting directly with the instances.

InterSystems staff + admins Hide everywhere
Hidden post for admin
Post a job Follow
Article sween · Feb 4 11m read

IKO Plus: HSSYS Mirroring with IKO

Enabling HSSYS Mirroring Out of the Gate with IKO

For those of us building InterSystems workloads on Kubernetes, we are definitely spoiled with the InterSystems Kubernetes Operator (IKO) doing the heavy lifting and mirroring on day one.  Where us spoiled brats jump up and down is when we try to add additional databases/namespaces when we provision from HealthConnect containers on day two, while others get to utilize HealthShare Mirroring for this task, the prerequisite of mirroring HSSYS out of the gate has been somewhat elusive.  Here is example on how you can this powerful feature up and running with the employment of IKO and IrisClusters.

#InterSystems Kubernetes Operator (IKO) #Kubernetes #Mirroring
1
0 43