Two commits are included in this PR:

• 1st commit (chore): asset data only — K8s version updates for GCP/IBM, IBM k8scluster enablement in cloud_conf.yaml, and AWS/GCP EKS/GKE node image type entries in cloudimage.csv
• 2nd commit (feat): the corresponding code changes for issue Kubernetes Node Image Management: Cross-CSP Analysis #2325 — redefine isKubernetesImage semantics for AWS/GCP, pass node image type identifiers to CB-Spider, and add input validation

Image Information Investigation Results Based on CSP CLI

Changes in Investigation Methodology

In the previous investigation, standard image information was collected by referencing AWS & GCP official documentation and CLI tools (aws CLI v2, gcloud CLI 559.0.0). This time, in addition to CLI tools, image information was further verified through each CSP's console.

Required Improvements to cloudimage.csv

The following issues were identified in the AWS/GCP entries of cloudimage.csv. For AWS, 5 image types require removal due to EOL or legacy reasons, and an additional 7 new image types are missing and need to be added. For GCP, 3 image types require removal. Details are explained in each section.

1. AWS EKS — Image Type Query Results via CLI

For the full list of CLI commands used in this investigation, see Reference — CLI Commands Used at the bottom of this document.

Actual CLI Response — aws ec2 describe-images Output (AL2023_x86_64_STANDARD example)

{
  "ImageId": "ami-0ab7e50653c9945f0",
  "Name": "amazon-eks-node-al2023-x86_64-standard-1.35-v20260224",
  "Description": "EKS-optimized Kubernetes node based on Amazon Linux 2023, (k8s: 1.35.0, containerd: 2.1.*)",
  "Architecture": "x86_64",
  "VirtualizationType": "hvm",
  "RootDeviceType": "ebs",
  "OwnerId": "602401143452",
  "State": "available",
  "CreationDate": "2026-02-24T...",
  "Public": true
}

cloudimage.csv Field Mapping (AWS)

Note: The cspImageName for AWS is a type identifier recognized by the EKS API.
It is used directly with the --ami-type option when creating node groups via aws eks describe-nodegroup or similar commands.
The actual AMI ID (ami-xxxxxxxxx) is resolved at runtime based on this type identifier.

AWS Full Image Type Query Summary (ap-northeast-2, as of 2026-02-24~03-04)

Each EKS image type has a dedicated 1:1 mapping to a specific AMI ID per Kubernetes version. For example, the AL2023_x86_64_STANDARD type has separate AMIs for each K8s version from 1.29 to 1.35, and the AMI IDs listed in the table represent the latest K8s version for each type.

The following 5 types should be removed from cloudimage.csv:

• AL2_x86_64, AL2_ARM_64, AL2_x86_64_GPU → Amazon Linux 2 EOL completed on 2025-06-30, no new AMIs being published
• UBUNTU_20_04, UBUNTU_22_04 → Canonical discontinued free AMI distribution; now Ubuntu Pro (paid subscription) only

The following 7 types need to be added to cloudimage.csv:

• BOTTLEROCKET_x86_64_NVIDIA, BOTTLEROCKET_ARM_64_NVIDIA → Bottlerocket-based NVIDIA GPU-optimized types (x86_64/arm64)
• AL2023_x86_64_NVIDIA, AL2023_ARM_64_NVIDIA → Amazon Linux 2023-based NVIDIA GPU-optimized types (x86_64/arm64)
• AL2023_x86_64_NEURON → Amazon Linux 2023-based AWS Inferentia/Trainium (Neuron) optimized type
• WINDOWS_CORE_2025_x86_64, WINDOWS_FULL_2025_x86_64 → Newly supported Windows Server 2025 types (Core/Full)

These are variant types (GPU/Neuron-optimized and Windows 2025) that fall outside the standard image type category and were omitted during the first investigation.
At the time of the first investigation, name filters were applied primarily for standard variants, which caused these types to be excluded from the query.
Their existence was confirmed through console queries in this round of investigation.

2. GCP GKE — Image Type Query Results via CLI

For the full list of CLI commands used in this investigation, see Reference — CLI Commands Used at the bottom of this document.

Actual CLI Response

gcloud container get-server-config response (image type related section)

defaultImageType: COS_CONTAINERD
validImageTypes:
  - COS_CONTAINERD
  - COS
  - UBUNTU
  - UBUNTU_CONTAINERD
  - WINDOWS_LTSC
  - WINDOWS_LTSC_CONTAINERD
  - WINDOWS_SAC
  - WINDOWS_SAC_CONTAINERD
defaultClusterVersion: 1.34.3-gke.1318000

gcloud compute images list response (COS-based OS image example)

{
  "name": "cos-stable-121-18867-381-14",
  "family": "cos-stable",
  "architecture": "X86_64",
  "diskSizeGb": "10",
  "status": "READY",
  "creationTimestamp": "2026-02-27T13:04:50.814-08:00",
  "description": "Google, Container-Optimized OS, 121-18867.381.14 stable, Kernel: COS-6.6.122 Kubernetes: 1.30.3 Docker: 27.5.1 Family: cos-stable"
}

cloudimage.csv Field Mapping (GCP)

Note: The cspImageName for GCP GKE is not a specific image.
There is no equivalent to AWS's AMI ID in GKE.
COS_CONTAINERD is a configuration selection value passed as --image-type=COS_CONTAINERD when creating a node pool;
the GKE platform internally selects the appropriate GCE VM image. This specific image is not exposed via public APIs.

The COS/Ubuntu images retrieved via gcloud compute images list are base OS images used by GKE,
and do not correspond 1:1 with GKE node images.

GCP Full Image Type Query Summary (asia-northeast3, as of 2026-02-27~03-04)

Unlike AWS, GKE image types do not follow a 1:1 mapping concept like per-K8s-version AMI IDs; they are configuration selection values passed via the --image-type parameter. GKE internally selects the appropriate image for each type.

The following 3 types should be removed from cloudimage.csv. This was confirmed both via GCP console inspection and by directly attempting to create node pools for each type using gcloud container node-pools create, which validated the removal reasons at the API level. Note that gcloud container get-server-config's validImageTypes returns all 8 types, so console visibility and API acceptance do not necessarily align:

• COS, UBUNTU → Legacy types based on Docker (dockershim) runtime. dockershim was officially removed in K8s 1.24. API rejection confirmed (code=400)
• WINDOWS_SAC_CONTAINERD → Windows Server SAC channel was officially announced as discontinued by Microsoft in 2021, with end-of-support (EOS) in June 2023. API rejection confirmed (code=400)
• WINDOWS_LTSC_CONTAINERD is grayed out in the console but accepted by the API — Windows node pools require a separate configuration path from Linux node pools, so it appears disabled only in the Linux node pool creation panel.

3. AWS vs GCP — Fundamental Differences in Image Architecture

Comparing the CLI query results from both CSPs reveals that the image type concepts of AWS EKS and GCP GKE are fundamentally different.

For AWS EKS, cspImageName is an AMI type identifier recognized by the EKS API (e.g., AL2023_x86_64_STANDARD), and each type maps 1:1 to a specific AMI ID (ami-xxxxxxxxx) per Kubernetes version — a concrete artifact that can be directly queried and verified via CLI.

In contrast, the cspImageName for GCP GKE is merely a configuration selection value (e.g., COS_CONTAINERD) passed via the --image-type option when creating a node pool. The GKE platform automatically selects the appropriate image internally, and that specific image is not exposed through public APIs. This makes it impossible to directly specify an image ID or establish a 1:1 correspondence with CLI results as in AWS.

Reference — CLI Commands Used

AWS (aws CLI v2, region: ap-northeast-2)

aws ec2 describe-images was used to collect detailed image information.
aws ssm get-parameter returns only a single AMI ID string, so it was not used for detailed field collection.

# AL2023, Windows variants — repeat query by changing name pattern per image type
aws ec2 describe-images \
  --owners amazon \
  --filters "Name=name,Values=amazon-eks-node-al2023-x86_64-standard-*" \
            "Name=state,Values=available" \
  --region ap-northeast-2 \
  --query "reverse(sort_by(Images, &CreationDate))[:3]" \
  --output json

# Note when querying Bottlerocket standard variants:
# The --filters name pattern also returns nvidia/fips variants,
# so jq post-processing is required to extract only standard AMIs.
# (AWS CLI Filters do not support negative conditions)

# BOTTLEROCKET_x86_64 — standard x86_64 (excluding nvidia, fips)
aws ec2 describe-images \
  --owners amazon \
  --filters "Name=name,Values=bottlerocket-aws-k8s-*-x86_64-v*" \
            "Name=state,Values=available" \
  --region ap-northeast-2 \
  --output json | jq '[.Images[] | select(.Name | test("nvidia|fips") | not)] | sort_by(.CreationDate) | reverse | .[:3] | {Name: .[].Name, ImageId: .[].ImageId}'

# BOTTLEROCKET_ARM_64 — standard aarch64 (excluding nvidia, fips)
aws ec2 describe-images \
  --owners amazon \
  --filters "Name=name,Values=bottlerocket-aws-k8s-*-aarch64-v*" \
            "Name=state,Values=available" \
  --region ap-northeast-2 \
  --output json | jq '[.Images[] | select(.Name | test("nvidia|fips") | not)] | sort_by(.CreationDate) | reverse | .[:3] | {Name: .[].Name, ImageId: .[].ImageId}'

# SSM Parameter Store — single AMI ID lookup (for reference)
# Output example: ami-0ab7e50653c9945f0
aws ssm get-parameter \
  --name "/aws/service/eks/optimized-ami/1.32/amazon-linux-2023/x86_64/standard/recommended/image_id" \
  --query "Parameter.Value" --output text

GCP (gcloud CLI 559.0.0, zone: asia-northeast3-a)

# Query GKE image type list (validImageTypes, defaultImageType, etc.)
gcloud container get-server-config \
  --zone=asia-northeast3-a \
  --format=json

# Base OS image query — COS family
gcloud compute images list \
  --project=cos-cloud \
  --filter="name~'^cos-' AND family:cos-stable AND status=READY" \
  --sort-by="~creationTimestamp" \
  --format=json --limit=3

# Base OS image query — Ubuntu family (x86_64)
gcloud compute images list \
  --filter="status=READY AND family:ubuntu-2204-lts" \
  --sort-by="~creationTimestamp" \
  --format=json --limit=3

# Base OS image query — Ubuntu family (ARM64)
gcloud compute images list \
  --filter="status=READY AND family:ubuntu-2204-lts-arm64" \
  --sort-by="~creationTimestamp" \
  --format=json --limit=3

Follow-up to PR #2332 (feat: redefine isKubernetesImage for AWS/GCP and update K8s cluster assets).

assets/cloudimage.csv

• Add missing AWS entries
• Remove EOL/legacy AWS entries and deprecated GCP entries
• Refine osType: add (ARM64) suffix for ARM64 entries (consistent with Azure convention)
• Refine osType: remove Full/Core from Windows osType; clarify in description instead
• Refine osType: Ubuntu → Ubuntu 22.04 LTS (GCP), Windows LTSC → Windows Server 2019 LTSC
• Enrich descriptions: add OS family, containerd runtime, and architecture info

src/core/infra/provisioning.go

• Remove AI-generated inline comment (// ✅ FIX: Assign imageId to request)

src/core/resource/k8scluster.go

• Remove getDefaultK8sImageName() which hardcoded AL2023_x86_64_STANDARD (AWS) and
  COS_CONTAINERD (GCP) as static fallbacks
• Delegate default node image handling to CB-Spider driver level instead:
  pass empty string when imageId is unspecified, letting each CSP driver apply
  its own default — avoids source-code changes when CSP updates image type identifiers

Test Results — AWS/GCP K8s Cluster Creation via MapUI

Performed end-to-end cluster creation tests via MapUI to validate the changes in this PR.

Test Summary

Details

• Cluster creation and node group addition completed successfully for both AWS (EKS) and GCP (GKE)
  using the image type identifiers registered in cloudimage.csv.
• However, the selected image type is currently not reflected in the MapUI display.

Fix: AWS EKS / GCP GKE node image types not appearing in cb-mapui image search

Root Cause

• When a VM spec is selected in cb-mapui, its architecture (x86_64 or arm64) is automatically applied as a SQL filter condition in the SearchImage() API
• EKS/GKE images stored with os_architecture = '' could not pass this filter, causing them to never appear in the cb-mapui image search list
• Unlike Azure images, AWS EKS / GCP GKE node image types cannot retrieve metadata such as os_architecture via CSP API, so they were stored in the DB with an empty string for os_architecture

Fix

• Added osArchitecture and osDistribution columns to cloudimage.csv and explicitly set values for AWS/GCP images where CSP API lookup is unavailable
• Azure images are left empty since their values are populated via CSP API
• This allows the SearchImage() architecture filter to keep its strict condition while correctly returning EKS/GKE images

DB Verification

• Verified directly in PostgreSQL after running cleanDB.sh → docker compose up → init.sh

Total registered images (535,577 total)

os_architecture / os_distribution stored values

-- AWS examples
aws | AL2023_ARM_64_STANDARD | arm64  | AL2023_ARM_64_STANDARD | k8s|kubernetes|container
aws | AL2023_x86_64_STANDARD | x86_64 | AL2023_x86_64_STANDARD | k8s|kubernetes|container
aws | BOTTLEROCKET_ARM_64    | arm64  | BOTTLEROCKET_ARM_64    | k8s|kubernetes|container

-- GCP examples
gcp | COS_CONTAINERD    | x86_64 | COS_CONTAINERD    | k8s|kubernetes|container
gcp | UBUNTU_CONTAINERD | x86_64 | UBUNTU_CONTAINERD | k8s|kubernetes|container

-- AZURE examples (populated by CSP API)
azure | Canonical:ubuntu-24_04-lts:server-arm64:... | arm64  | ubuntu-24_04-lts:server-arm64 | vm
azure | Canonical:ubuntu-24_04-lts:server:...       | x86_64 | ubuntu-24_04-lts:server       | vm

⚠️ Additional Fix: Removed Azure Oracle Linux image

• During verification, Oracle:Oracle-Linux:ol93-arm64-lvm-gen2:9.3.3 was found to have empty os_architecture and os_distribution in the DB
• Root cause: Oracle has discontinued Oracle Linux distribution on Azure Marketplace, causing the CSP API to return ImageVersionDeprecated (404)
• The entry has been removed from cloudimage.csv

VM Image from publisher: Oracle with - Offer: Oracle-Linux,
Sku: ol93-arm64-lvm-gen2, Version: 9.3.3 is deprecated.

@hanizang77 Could you check why other commits have been included this PR? https://github.com/cloud-barista/cb-tumblebug/pull/2332/commits

@seokho-son

Sorry for the confusion caused by the messy branch history.

I've force-pushed a cleaned-up version that includes only my 4 intended commits, with duplicate commits removed.

Thank you for your review!

/approve