Kubernetes (commonly stylized as k8s) is an open-source container-orchestration system for automating application deployment, scaling, and management. It aims to provide a platform for automating deployment, scaling, and operations of application containers across clusters of hosts. It works with a range of container tools, including Docker.
With the world (as well as our own technology) moving to the cloud at such a fast pace it is easy (at least for myself) to get caught up in the little details. One thing I, and some clients of ours, had run into a couple of times was the necessity to specify the version of the images one plans to use with the IKO.
InterSystems Kubernetes Operator (IKO) 3.6 is now Generally Available. IKO 3.6 adds significant new functionality along with numerous bug fixes. Highlights include:
I want to deploy IRIS apps running in containers in Kubernetes with user accounts configured.
I have a %ZSTART routine which looks for an XML file with Users export data and if the %ZSTART routine finds this file, it imports it. This Users export data can be obtained by running a class method.
I have defined a task which can be scheduled or run on demand. This tasks imports user data from an XM file.
In Kubernetes I can provide a ConfigMap to stage the Users data for the %ZSTART routine.
And I did not find a restriction on the use of Ensemble 2018 installed on Docker with Openshift, but I received information that Intersystems would not support this installation case. That is true?
I'm trying to learn how to use the IKO for deploying solutions to Kubernetes. In my current project I'm trying to deploy the IAM onto a K8S context. Are there directly usable samples of the yaml file I need to use for that?
I am new to IRIS, IKO and IAM. I have read through a lot of the documentation, but I need clarity on some things that I can't find in the documentation.
InterSystems Kubernetes Operator (IKO) 3.5 is now Generally Available. IKO 3.5 adds significant new functionality along with numerous bug fixes. Highlights include:
This week I was able to demo a proof of concept for our FMS interface on traffic cop architecture to my team. We are working on modernizing an Interoperability production running on mirrored Health Connect instances. We deploy IRIS workloads on Red Hat OpenShift Container Platform using InterSystems Kubernetes Operator (IKO). We can define any number of replicas for the compute stateful set where each compute pod runs our Interoperability production. We introduced Horizontal Pod Autoscaler (HPA) to scale up the number of compute pods based on memory or CPU utilization.
IRIS configurations and user accounts contain various data elements that need to be tracked, and many people struggle to copy or sync those system configurations and user accounts between IRIS instances. So how can this process be simplified?
In software engineering, CI/CD or CICD is the set of combined practices of continuous integration (CI) and (more often) continuous delivery or (less often) continuous deployment (CD). Can CI/CD eliminate all our struggles?
Watch this video to get a brief overview of the near- and long-term plans for HealthShare containerization and Kubernetes adoption, as well as a preview/demo of our current progress.
I'm thinking to deploy healthshare using kubernetes. Has any one done this before? How will the TCP listeners in healthshare work with kubernetes? Will they automatically create a service endpoint so that I can route traffic?
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:
The InterSystems Kubernetes Operation (IKO) version 3.3 is now available via the WRC download page and the InterSystems Container Registry.
IKO simplifies working with InterSystems IRIS or InterSystems IRIS for Health in Kubernetes by providing an easy-to-use irisCluster resource definition. See the documentation for a full list of features, including easy sharding, mirroring, and configuration of ECP.
IKO 3.3 Highlights:
Support for 2021.2 and 2022.1 editions of InterSystems IRIS & IRIS for Health
Support for Kuberentes 1.21
Deploy common System Alerting and Monitoring (SAM) configurations as part of your irisCluster
InterSystems API Manager (IAM) can now also be deployed and managed as part of the irisCluster
Automatic tagging of mirror pair active side, so a service can always point to the active mirror member.
Did you catch an Experience Lab at the 2021 Virtual Summit? Head over to the InterSystems Learning siteto access all four of these hands-on exercises, and get up to speed on:
Watch as the presenter uses IKO to deploy the WebGateway, SAM, and InterSystems API Manager with the latest version of the InterSystems Kubernetes Operator:
Hi All! For those of you who attended experience labs at the 2021 Virtual Summit, you may recall that one of the lab sessions was around Kubernetes. We've now converted that lab to be fully on-demand. You can launch a small cluster of VMs and follow the exercise to manage your Kubernetes cluster, deploy InterSystems IRIS containers to it, and watch its self-healing nature when destroying a pod.
Want a commercial grade FHIR® Implementation included in your micro service ecosystem and barely have enough time to fill out your Health plan elections?
Does InterSystems have any best practices for deploying IRIS into Kubernetes? For example one question we have is should IRIS have a dedicated AKS cluster or can it be added to an existing cluster?
In this article, we’ll look at one of the ways to monitor the InterSystems IRIS data platform (IRIS) deployed in the Google Kubernetes Engine (GKE). The GKE integrates easily with Cloud Monitoring, simplifying our task. As a bonus, the article shows how to display metrics from Cloud Monitoring in Grafana.
Note that the Google Cloud Platform used in this article is not free (price list), but you can leverage a free tier. This article assumes that you already have a project in the Google Cloud Platform (referred to as <your_project_id>) and have permission to use it.
Episode 20 of Data Points features a conversation with Bob Kuszewski about the Kubernetes and the InterSystems Kubernetes Operator (IKO). Take a listen to hear about some of the use cases and features of IKO, plus how it compares to InterSystems Cloud Manager (ICM) within the cloud space.
If you're looking for an introduction to Kubernetes as a technology, and a little teaser about the InterSystems Kubernetes Operator, check out the recently released Kubernetes Overview video. This video will introduce you to the functionality and use cases of Kubernetes, and explain a bit about how the InterSystems Kubernetes Operator makes it beneficial to use Kubernetes with InterSystems IRIS.
By update
Open Exchange app