#Kubernetes

Hi Everyone,

Are you ready yet? Have you packed all you'll need for the summit? And don't forget the needed power-socket adapters if you come from outside the US!

Have you signed up for the Container Bootcamp on Sunday? Or one of the various Experience Labs, the many informative sessions and one of the symposia on Wednesday afternoon?

Again, there is a mobile app for attendees that should help you keep it all under control and even allow you to book time with InterSystems personnel for a one-on-one deep-dive on whatever you need.

Hi Community!

We're pleased to invite you to the DockerCon 2019 – the #1 container industry conference for all things Kubernetes, microservices, and DevOps. The event will be held at the Moscone Center in San Francisco from April 29 to May 2.

In addition, there will be a special session "Containerized Databases for Enterprise Applications" presented by @Thomas Carroll, Product Specialist at InterSystems.

See the details below.

Hi

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?

Please advise me on how to think about this.

Thanks

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.

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:

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.

Hi Developers,

Please welcome the new video from Global Summit 2019 on InterSystems Developers YouTube:

⏯ InterSystems IRIS Cloud Roadmap

https://www.youtube.com/embed/2qvqZzI4xy8
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

We have solution which uses IRIS with IAM and webgateway integrated.

After integration, we notice that in the kong configuration in the kongdb upstreams are not created as listed in the kong.yml

We noticed that, IAM api calls are failing with enterprise license expired.

[kong@iam-deployment-75f485954c-ssdfv /]$ curl --location --request POST 'http://localhost:8001/services/'
{"message":"Enterprise license missing or expired"}

From Logs:

As an IT and cloud team manager with 18 years of experience with InterSystems technologies, I recently led our team in the transformation of our traditional on-premises ERP system to a cloud-based solution. We embarked on deploying InterSystems IRIS within a Kubernetes environment on AWS EKS, aiming to achieve a scalable, performant, and secure system. Central to this endeavor was the utilization of the AWS Application Load Balancer (ALB) as our ingress controller.

Hi Developers,

Enjoy watching the new video on InterSystems Developers YouTube:

⏯ Diving into InterSystems Cloud Technology

https://www.youtube.com/embed/Twg7IESeyhQ
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

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

InterSystems Kubernetes Operator (IKO) 3.6 is now Generally Available. IKO 3.6 adds significant new functionality along with numerous bug fixes. Highlights include:

Hi Community!

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

The IKO allows for sidecars. The idea behind them is to have direct access to a specific instance of IRIS. If we have mirrored data nodes, the web gateway will (correctly) only give us access to the primary node. But perhaps we need access to a specific instance. The sidecar is the solution.

Building on the example from the previous article, we introduce the sidecar by using a mirrored data node and of course arbiter.