In this section
v6.10.0
Released: March 4, 2025
6.10.0 (2025-03-04)
SmoothGlue Features
- This release adds optional basic support for Amazon Linux 2023 (AL2023) AMIs in EKS cluster IaC. To use AL2023, add the following to the
cluster_inputssection of yourenv.hclfile:locals {cluster_inputs = {ami_id = "ami-0123456789abcdef0" # replace with actual AMI IDdefault_ami_type = "AL2023_x86_64_STANDARD"}}- For more details, refer to How to Create an EKS Cluster with Amazon Linux 2023.
- This release adds optional support in IaC for provisioning GitLab's database using an RDS Multi-AZ cluster rather than a single database instance. As a single instance, RDS offers support for a single warm standby instance; however, provisioning the database using an RDS Multi-AZ cluster allows for a cluster of three instances. There is no automatic migration path from a single RDS instance to a Multi-AZ cluster, so we recommend enabling the Multi-AZ cluster during the initial cluster provision if possible. If migrating an existing cluster, you will need to perform a database import/export manually.
- Note that there are instance class limitations when using a Multi-AZ RDS cluster; see the AWS documentation for more information.
⏩ Upgraded Packages
- This release of SmoothGlue Enterprise v6.10.0 includes Big Bang Version 2.47.0. For more details on the features and updates included in Big Bang Version 2.47.0, please refer to the Big Bang Release Notes.
- Update Confluence to LTS 9.2.1 (Helm chart version 1.22.5-bb.0).
- Update Jira to LTS 10.3.3 (Helm chart version 1.22.5-bb.1).
🪲 Bug Fixes
- Refactor IaC compatibility mode toggle to correctly disable NLB stickiness in ISO regions.
- Exclude
aws-ebs-csi-drivernamespace fromgenerate-networkpolicy-imdsKyverno ClusterPolicy so that RKE2 clusters can provision EBS PVCs correctly. - Exclude the following namespaces from the
require-istio-on-namespacesKyverno ClusterPolicy so that users may enforce the policy:cluster-autoscalercrossplane-systemkyvernostructsure-system
- Extend HelmRelease install timeout for GitLab to 15 minutes.
❗️ Known Issues
- When using a network load balancer (NLB) with the
preserve_client_ipoption enabled, the default routing rules for EKS and RKE2 nodes prevent nodes from accessing platform services hosted on the same node, which can cause failures when logging into Keycloak, particularly on clusters with fewer nodes.- More specifically, the default routing rules for nodes do not route traffic to the VPC router for traffic within the node's local subnet, since these addresses should theoretically be reachable directly by the node. However, when using the
preserve_client_ipoption, the VPC router rewrites the source IP for traffic; when the node attempts to talk to the NLB, the traffic is rewritten so that it appears to come from the node itself, and the return traffic is not able to be routed correctly back to the NLB. - We are currently working on an Istio-level fix which should prevent VirtualService traffic within the cluster from ever leaving the cluster. Until that fix is available, the following options are potential workarounds:
- Disabling the
preserve_client_ipoption on the NLB will resolve the issue at the cost of losing source attribution for incoming traffic. - Removing the local subnet route on nodes will resolve the issue at the cost of increasing the amount and cost of traffic being routed through the VPC router.
- Increasing the node count for the cluster will reduce the likelihood of the issue because it will become less likely for any given traffic to be routed back to the original node.
- Disabling the
- More specifically, the default routing rules for nodes do not route traffic to the VPC router for traffic within the node's local subnet, since these addresses should theoretically be reachable directly by the node. However, when using the
🌐 Compatibility
- The packages for this release were built using Zarf v0.46.0.
- The packages were tested across the following Kubernetes distributions:
- RKE2:
v1.30.9-rke2r1 - K3s:
v1.30.9+k3s1 - EKS:
v1.30.8
- RKE2:
- The following AMI versions were used for testing:
- RKE2 AMI:
smoothglue-rke2-v1.30.9-rke2r1-rocky-8-base-v1.1.1-stig-2025-02-17T09-24-30Z - EKS AMI:
smoothglue-eks-1.30.8-rocky-8-base-v1.1.1-stig-2025-02-10T09-21-19Z - Base AMI:
base-Rocky-8-EC2-LVM-v1.1.1-stig-2025-02-10T0802
- RKE2 AMI:
🔗 Helpful Links
- Refer to the SmoothGlue documentation for additional guidance.
- For details on the Big Bang release, see the Big Bang Release Notes.