#Kubernetes

Hi Community,

We're pleased to invite you to the upcoming webinar in Spanish called "Deployments in Kubernetes with High Availability".

Date & Time: October 20, 4:00 PM CEST

Speaker: @Alberto Fuentes, Sales Engineer, InterSystems Iberia

Hey Developers,

We're pleased to invite you to join the next InterSystems IRIS 2020.1 Tech Talk: DevOps on June 2nd  at 10:00 AM EDT! 

In this InterSystems IRIS 2020.1 Tech Talk, we focus on DevOps. We'll talk about InterSystems System Alerting and Monitoring, which offers unified cluster monitoring in a single pane for all your InterSystems IRIS instances. It is built on Prometheus and Grafana, two of the most respected open source offerings available.

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.

Hey Developers,

Enjoy watching the new video on InterSystems Developers YouTube channel:

⏯ Smart Data Services (Vision & Demo)

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:

Did you catch an Experience Lab at the 2021 Virtual Summit? Head over to the InterSystems Learning site to access all four of these hands-on exercises, and get up to speed on:

Hey Developers,

Watch as the presenter uses IKO to deploy the WebGateway, SAM, and InterSystems API Manager with the latest version of the InterSystems Kubernetes Operator: 

⏯ IKO: The InterSystems Kubernetes Operator (Version 3.0)

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.

It's a great introduction to Kubernetes if you are interested! See here: Achieving High Availability with InterSystems IRIS and Kubernetes

We’ve already considered how to run an IRIS-based application in GCP Kubernetes in Deploying InterSystems IRIS Solution into GCP Kubernetes Cluster GKE Using CircleCI. Additionally, we’ve seen how to run an IRIS-based application in AWS Kubernetes in Deploying a Simple IRIS-Based Web Application Using Amazon EKS. Now, let’s look at how to deploy an application to the Azure Kubernetes Service (AKS).

Want a commercial grade FHIR® Implementation included in your micro service ecosystem and barely have enough time to fill out your Health plan elections?

Here is a quick way to invite the InterSystems® FHIR®Accelerator Service to your Kubernetes Microservice party for immediate use. The solution uses Nginx proxy ninja moves to get the job done. Though rustic and bound to create some technical arguments, I am pretty happy with the results until this community tells me otherwise, so FHIR® away as they say but it would be great if you heard me out first.

Disclaimer

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?

David

IntroductionSeveral resources tell us how to run IRIS in a Kubernetes cluster, such as Deploying an InterSystems IRIS Solution on EKS using GitHub Actions and Deploying InterSystems IRIS solution on GKE Using GitHub Actions. These methods work but they require that you create Kubernetes manifests and Helm charts, which might be rather time-consuming.To simplify IRIS deployment, InterSystems developed an amazing tool called InterSystems Kubernetes Operator (IKO). A number of official resources explain IKO usage in details, such as  New Video: Intersystems IRIS Kubernetes Operator and

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. 

Hey Developers,

New video is already on InterSystems Developers YouTube:

⏯ Deploying & Upgrading IRIS with Kubernetes Operator

Hi Developers,

The new video from Global summit 2019 is already on InterSystems Developers YouTube:

⏯ Intersystems IRIS Kubernetes Operator

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.

I am pleased to announce the availability of InterSystems Container Registry. This provides a new distribution channel for customers to access container-based releases and previews. All Community Edition images are available in a public repository with no login required. All full released images (IRIS, IRIS for Health, Health Connect, System Alerting and Monitoring, InterSystems Cloud Manager) and utility images (such as arbiter, Web Gateway, and PasswordHash) require a login token, generated from your WRC account credentials.

greetings Community!

InterSystems Learning Services is working to identify and create libraries of high-quality learning resources for third-party technologies, platforms, and systems that are part of, integrated with, or commonly used with InterSystems products and technologies. we don't create content for these ourselves, but want to support our clients, external and internal, in learning about them and how to use them.

Hi Community,

Please welcome the new video on InterSystems Developers YouTube:

⏯ Deploying InterSystems IRIS Solutions into Kubernetes Google Cloud

In the context of IKO (Iris Kubernetes Operator) the question of Service not redirecting dynamically to the correct Pod is still pending.
In production this can be dangerous since an overload (or any other simpler problem) can cause you to change the main Pod and leave the application inoperable until we intervene.

Intersystems support warned that this is still an issue of IKO, but there are some possibilities that I am studying.

To explore an idea I had, I would like the help of this Forum to answer the following question:

Hi colleagues!

Every day Johns Hopkins University publishes new data on coronavirus COVID-19 pandemic status.

I built a simple InterSystems IRIS Analytics dashboard using InterSystems IRIS Community Edition in docker deployed on GCP Kubernetes which shows key measures of the disease outbreak.

This dashboard is an example of how information from CSV could be analyzed with IRIS Analytics and deployed to GCP Kubernetes in a form of InterSystems IRIS Community Edition.

Added the interactive map of the USA:

In theprevious article, we looked at one way to create a custom operator that manages the IRIS instance state. This time, we’re going to take a look at a ready-to-go operator, InterSystems Kubernetes Operator (IKO).Official documentation will help us navigate the deployment steps.

Hi Community!

We are pleased to invite you to the upcoming webinar in Spanish: "Improving Kubernetesperformance", on December 9, at 4:00 PM (CET).

This article is a continuation of Deploying InterSystems IRIS solution on GKE Using GitHub Actions, in which, with the help of GitHub Actions pipeline, our zpm-registry was deployed in a Google Kubernetes cluster created by Terraform. In order not to repeat, we’ll take as a starting point that:

Imagine you want to see what InterSystems can give you in terms of data analytics. You studied the theory and now you want some practice. Fortunately, InterSystems provides a project that contains some good examples: Samples BI. Start with the README file, skipping anything associated with Docker, and go straight to the step-by-step installation. Launch a virtual instance, install IRIS there, follow the instructions for installing Samples BI, and then impress the boss with beautiful charts and tables. So far so good. 

Inevitably, though, you’ll need to make changes.

In an earlier article (hope, you’ve read it), we took a look at the CircleCI deployment system, which integrates perfectly with GitHub. Why then would we want to look any further? Well, GitHub has its own CI/CD platform called GitHub Actions, which is worth exploring. With GitHub Actions, you don’t need to rely on some external, albeit cool, service.

In this article we’re going to try using GitHub Actions to deploy the server part of  InterSystems Package Manager, ZPM-registry, on Google Kubernetes Engine (GKE).

Last time we deployed a simple IRIS application to the Google Cloud. Now we’re going to deploy the same project to Amazon Web Services using its Elastic Kubernetes Service (EKS).

We assume you’ve already forked the IRIS project to your own private repository. It’s called <username>/my-objectscript-rest-docker-template in this article. <root_repo_dir> is its root directory.

Most of us are more or less familiar with Docker. Those who use it like it for the way it lets us easily deploy almost any application, play with it, break something and then restore the application with a simple restart of the Docker container.InterSystems also likes Docker.The InterSystems OpenExchange projectcontains a number of examples that run InterSystems IRIS images in Docker containers that are easy to download and run. You’ll also find other useful components, such as the Visual Studio IRIS plugin.It’s easy enough to run IRIS in Docker with additional code for specific use cases, but

Hi Developers,

Enjoy watching the new video on InterSystems Developers YouTube:

⏯ Diving into InterSystems Cloud Technology