Upgrade strimzi-kafka pack to 1.1.0

[svalenciah19]

Upgrade strimzi-kafka pack to 1.1.0

[vishwanaths]

Pack review — strimzi-kafka-operator-1.1.0

Packs Validation: ❌ FAILURE (run https://github.com/spectrocloud/pack-central/actions/runs/30941227584) — individual errors listed under Blockers below
source annotation: ✅ community
Pack metadata: name=strimzi-kafka version=1.1.0 addonType=system app layer=addon displayName=Strimzi Kafka contributor=spectrocloud

Compared against packs/strimzi-kafka-operator-1.0.0/

Summary of differences

• pack.json: version 1.0.0 → 1.1.0 (minor bump); charts entry updated to charts/strimzi-kafka-operator-helm-3-chart-1.1.0.tgz. No other top-level keys changed (annotations, cloudTypes, addonType, layer, displayName, constraints all identical).
• values.yaml: image tags bumped to 1.1.0 across pack.content.images (operator, kafka, kafka-bridge, kaniko-executor, maven-builder); kafka:*-kafka-4.1.2 replaced with kafka:1.1.0-kafka-4.2.1; charts.strimzi-kafka-operator.defaultImageTag bumped to 1.1.0; operatorNetworkPolicy.egress changed from {} to - {} (list form). No new/removed top-level keys.
• charts: strimzi-kafka-operator-helm-3-chart-1.0.0.tgz (124,029 B) replaced by strimzi-kafka-operator-helm-3-chart-1.1.0.tgz (124,717 B) — +688 B (+0.6%). Tarball contents were not inspected, but the PR also unpacks the chart into charts/strimzi-kafka-operator/ for the first time (new sub-tree with CRDs, templates, grafana dashboards, README, Chart.yaml, values.yaml).
• logo.png: unchanged (same blob sha).
• Files added under the pack directory: README.md (top-level, 216 lines) and the entire unpacked charts/strimzi-kafka-operator/ sub-tree (CRDs, templates, grafana dashboards, helpers, chart values, etc.).
• Files removed: none.

pack.json diff

@@ -6,7 +6,7 @@
     "contributor" : "spectrocloud"
   },
   "charts": [
-    "charts/strimzi-kafka-operator-helm-3-chart-1.0.0.tgz"
+    "charts/strimzi-kafka-operator-helm-3-chart-1.1.0.tgz"
   ],
   "cloudTypes": [
     "all"
@@ -14,7 +14,7 @@
   "displayName": "Strimzi Kafka",
   "layer":"addon",
   "name": "strimzi-kafka",
-  "version": "1.0.0",
+  "version": "1.1.0",

values.yaml diff

@@ -3,17 +3,17 @@
 pack:
   content:
     images:
-      - image: quay.io/strimzi/operator:1.0.0
-      - image: quay.io/strimzi/kafka:1.0.0-kafka-4.1.2
-      - image: quay.io/strimzi/kafka:1.0.0-kafka-4.2.0
-      - image: quay.io/strimzi/kafka-bridge:1.0.0
-      - image: quay.io/strimzi/kaniko-executor:1.0.0
-      - image: quay.io/strimzi/maven-builder:1.0.0
+      - image: quay.io/strimzi/operator:1.1.0
+      - image: quay.io/strimzi/kafka:1.1.0-kafka-4.2.1
+      - image: quay.io/strimzi/kafka:1.1.0-kafka-4.2.0
+      - image: quay.io/strimzi/kafka-bridge:1.1.0
+      - image: quay.io/strimzi/kaniko-executor:1.1.0
+      - image: quay.io/strimzi/maven-builder:1.1.0

     charts:
       - repo: https://strimzi.io/charts
         name: strimzi-kafka-operator
-        version: 1.0.0
+        version: 1.1.0
@@ -31,7 +31,7 @@ charts:

     defaultImageRegistry: quay.io
     defaultImageRepository: strimzi
-    defaultImageTag: 1.0.0
+    defaultImageTag: 1.1.0

@@ -121,7 +121,8 @@ charts:
       #
       # Any meaningful network restrictions must be defined per cluster,
       # with a full knowledge of the Kafka topology and port configuration.
-      egress: {}
+      egress:
+      - {}

Blockers

• Packs Validation: Image manifest fetch failed. quay.io/strimzi/kafka-bridge:1.1.0 may not be a valid image: MANIFEST_UNKNOWN: manifest unknown at https://quay.io/v2/strimzi/kafka-bridge/manifests/1.1.0. The strimzi/kafka-bridge project versions independently from the operator — please update the pack.content.images entry to a tag that actually exists on quay.io (e.g. the latest released kafka-bridge tag). Note that charts.strimzi-kafka-operator.kafkaBridge.image.tag in values.yaml is still 1.0.0, which suggests the intent was not to bump kafka-bridge in lockstep with the operator.
• Packs Validation: Image content verification failed for packs/strimzi-kafka-operator-1.1.0. Make sure you have an image: array defined under the images: section of values.yaml. The pack.content.images list is present, so this most likely cascades from the failed manifest fetch above — re-run validation once the kafka-bridge tag is corrected.

Nits / observations

• charts.strimzi-kafka-operator.kafkaBridge.image.tag is still 1.0.0 while the top-level pack.content.images was bumped to kafka-bridge:1.1.0. Please align the two once you settle on the correct kafka-bridge tag.
• operatorNetworkPolicy.egress changed from {} (map) to a YAML list containing an empty map (- {}). Confirm this matches the upstream Strimzi chart's expected schema for egress — the surrounding comments say {} is meant to be an "unrestricted" placeholder.
• This PR also commits the fully unpacked helm chart under charts/strimzi-kafka-operator/ alongside the .tgz. Prior versions (0.40.0, 1.0.0) shipped only the tarball. If this is intentional, it's fine; if not, consider removing the unpacked tree to keep the pack lean.

Review generated by the pack-reviewer Claude Code subagent.