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.
I am currently using IKO 3.6 to deploy an irisCluster on EKS, but I am facing some challenges. Firstly, I need assistance in understanding how to connect to the Web Gateway sidecar. If anyone has experience with this, I would greatly appreciate any guidance or advice you can offer. Secondly, I am trying to utilize the 'seed: path' options of irisDatabases, but I am unsure of the best approach. If anyone has successfully implemented this feature, I would love to hear about your approach and any insights you can provide. Thank you in advance for any help you can offer!
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.
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:
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?
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.
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:
I've been working on deploying an IRIS for Health environment in EKS. There is a video session in the InterSystems learning portal about this feature but I have not succeeded in finding the proper documentation and resources to use this in my Kubernetes cluster.
Has this been deprecated/discontinued? Any idea where can I find the resources? Should I stick to StatefulSets instead of using the IrisCluster resource type provided by this operator?
Just got the new beta version of Docker, with depreciation warning of AUFS. It's so bad news when InterSystems does not support used by default storage driver overlay2. Recently I thought to play with Google Kubernetes Engine, and realized that I can't work with InterSystems products there due to incompatibility with Storage Driver. Maybe it's already time to think about support?
By update
