⚠️ Deletes existing SKE cluster and kubeconfig resources (020-ske-cluster.tf) — this will destroy the cluster and its data.
⚠️ Deletes Promtail Helm release and monitoring namespace (040-promtail.tf) — removes log collection from the cluster.
Creates new SKE cluster with dynamic Kubernetes and OS versions, using variables for configuration (030-ske-cluster.tf).
Creates new Observability instance with alert config using variable for email (040-observability.tf).
Creates new Alloy Helm release with secure credential handling via Kubernetes Secret (050-alloy.tf).
Creates new log alert group with variable-based namespace (060-log-alertgroup.tf).
Creates new example workload namespace and pod with variable-based namespace (070-example-workload.tf).
Adds variables for flexible configuration (020-variables.tf).
Updates provider versions to newer releases (010-provider.tf).

# To avoid destructive deletion, rename the old cluster resources instead of deleting them
resource "stackit_ske_cluster" "example_old" {
  # ... keep old config but rename resource
}

resource "stackit_ske_kubeconfig" "example_old" {
  # ... keep old config but rename resource
}

# Then create the new cluster under a new name or with updated config
resource "stackit_ske_cluster" "example" {
  # ... new config using variables
}

✅ 🔒 Security Review

🤖 STACKIT Model Serving

✅ No security issues found.

✅ 📐 Example Consistency

🤖 STACKIT Model Serving

✅ Example follows repository conventions.

✅ 📚 Example README

🤖 STACKIT Model Serving

✅ Example READMEs are complete.

⚠️ 💬 Commit Messages

🤖 STACKIT Model Serving

"fix(ske): refactor observability logs with alloy | adjust agents.md" → Suggest: "Refactor SKE observability logs to use Alloy and update agents.md documentation"
"fix(ske): refactor observability logs with alloy" → Suggest: "Refactor SKE observability logging to integrate Alloy for improved metrics and tracing"

✅ 🏷️ Tag Quality

🤖 STACKIT Model Serving

The tag promtail in the README.md should be replaced with alloy to accurately reflect the current log shipping agent used.
The tag list is otherwise accurate and covers the STACKIT products (ske, observability) and key technologies (logging, alerting, kubernetes).
All tags are lowercase and hyphen-separated.

✅ README tags accurately reflect the content.

Generated automatically — treat as a hint, not a gate.

## 🤖 AI PR Review > [`9c2707ae`](https://professional-service.git.onstackit.cloud/professional-service-best-practices/professional-service/commit/9c2707ae9a5afe1830458ac6ebc217f1a93244e0) · STACKIT Model Serving <details> <summary>✅ 📝 Spelling & Grammar</summary> <details> <summary>🤖 STACKIT Model Serving</summary> ✅ No spelling or grammar issues found. </details> </details> <details> <summary>⚠️ 🏗️ Infrastructure Changes</summary> <details> <summary>🤖 STACKIT Model Serving</summary> - ⚠️ Deletes existing SKE cluster and kubeconfig resources (020-ske-cluster.tf) — this will destroy the cluster and its data. - ⚠️ Deletes Promtail Helm release and monitoring namespace (040-promtail.tf) — removes log collection from the cluster. - Creates new SKE cluster with dynamic Kubernetes and OS versions, using variables for configuration (030-ske-cluster.tf). - Creates new Observability instance with alert config using variable for email (040-observability.tf). - Creates new Alloy Helm release with secure credential handling via Kubernetes Secret (050-alloy.tf). - Creates new log alert group with variable-based namespace (060-log-alertgroup.tf). - Creates new example workload namespace and pod with variable-based namespace (070-example-workload.tf). - Adds variables for flexible configuration (020-variables.tf). - Updates provider versions to newer releases (010-provider.tf). ```hcl # To avoid destructive deletion, rename the old cluster resources instead of deleting them resource "stackit_ske_cluster" "example_old" { # ... keep old config but rename resource } resource "stackit_ske_kubeconfig" "example_old" { # ... keep old config but rename resource } # Then create the new cluster under a new name or with updated config resource "stackit_ske_cluster" "example" { # ... new config using variables } ``` </details> </details> <details> <summary>✅ 🔒 Security Review</summary> <details> <summary>🤖 STACKIT Model Serving</summary> ✅ No security issues found. </details> </details> <details> <summary>✅ 📐 Example Consistency</summary> <details> <summary>🤖 STACKIT Model Serving</summary> ✅ Example follows repository conventions. </details> </details> <details> <summary>✅ 📚 Example README</summary> <details> <summary>🤖 STACKIT Model Serving</summary> ✅ Example READMEs are complete. </details> </details> <details> <summary>⚠️ 💬 Commit Messages</summary> <details> <summary>🤖 STACKIT Model Serving</summary> - "fix(ske): refactor observability logs with alloy | adjust agents.md" → Suggest: "Refactor SKE observability logs to use Alloy and update agents.md documentation" - "fix(ske): refactor observability logs with alloy" → Suggest: "Refactor SKE observability logging to integrate Alloy for improved metrics and tracing" </details> </details> <details> <summary>✅ 🏷️ Tag Quality</summary> <details> <summary>🤖 STACKIT Model Serving</summary> - The tag `promtail` in the README.md should be replaced with `alloy` to accurately reflect the current log shipping agent used. - The tag list is otherwise accurate and covers the STACKIT products (ske, observability) and key technologies (logging, alerting, kubernetes). - All tags are lowercase and hyphen-separated. ✅ README tags accurately reflect the content. </details> </details> --- _Generated automatically — treat as a hint, not a gate._