PSA: Externally managed Istio 1.25.3 tested as working for deployKF 0.15.0 (+tips pre EKS 1.31 upgrade) #257
Unanswered
berglh
asked this question in
Questions & Answers
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
EKS 1.30 is entering extended maintenance next week, and prior to updating to 1.31, we upgraded Istio to version 1.25.3 (that officially supports Kubernetes 1.31). #254 also shows that EKS 1.31 is working with deployKF.
ℹ️We are only running the Kubeflow notebooks app currently and not using Pipelines and ML compoments. Please ensure you check the
istioctlanalysis commands before proceeding.We also run our own Istio Ingress Gateway deployment, let deployKF manage its Istio Gateway resource and have a separate Istio Gateway resource for our other apps like self-managed ArgoCD and Airflow. We also run the Istio CNI chart for the cluster but have left the sidecar operation for deployKF components.
Pre-Upgrade
ℹ️Before upgrading Istio, it's always recommended to use
istioctlto check for upgrade compatibility issues. Download the latest version of theistioctl: Install istioctl. Once installed, run the following commands:Check the output for any issues, take careful note of any compatibility issues, particularly if they may impact the operation of deployKF & Kubeflow.
Issues
When I updated the Helm chart for Istio we deploy with Terraform, we ran into a few minor issues:
ISTIO_META_DNS_AUTO_ALLOCATEproxyMetadata setting in meshConfig is deprecated, we removed this from the primary Istio chart.platform=awsfrom our Istio gateway chart (it was an invalid value, standard chart works).Other Notes
deploykf-authnamespace resolved the issue.Beta Was this translation helpful? Give feedback.
All reactions