chore: chart version bump (#165) (#166)

* chore: chart version bump and docs update

* fix: linting on errors on pr title

Author: lockwobr

.github/workflows/commit-linting.yaml

@@ -15,7 +15,9 @@
 # limitations under the License.
 
 name: Commit Linting
-on: pull_request
+on: 
+  pull_request:
+    types: [opened, edited, reopened, synchronize, ready_for_review]
 jobs:
   commit-linting:
     name: Git commit linting

README.md

@@ -72,7 +72,7 @@ helm search repo skyhook ## should show the latest version
 
 # basic install
 helm install skyhook skyhook/skyhook-operator \
-  --version v0.12.0 \
+  --version v0.12.1 \
   --namespace skyhook \
   --create-namespace
 ```

chart/Chart.yaml

@@ -5,9 +5,9 @@ type: application
 # This is the chart version. This version number must be incremented each time you make changes to the helm chart. OR
 # it the agent version is updated, or operator version is updated.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: v0.12.0
+version: v0.12.1
 # This is the version number operator container being deployed.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-appVersion: v0.12.0
+appVersion: v0.12.1
 # this is the minimum version of kubernetes that the operator supports/tested against.
 kubeVersion: ">=1.30.0-0"

chart/values.yaml

@@ -84,8 +84,8 @@ controllerManager:
       pauseImage: registry.k8s.io/pause:3.10
     image:
       repository: nvcr.io/nvidia/skyhook/operator
-      tag: "v0.12.0" ## if both tag and digest are omitted, defaults to the chart appVersion
-      digest: "sha256:ce79a9778fca453e54d58506c71c8ff6765b65d44a73fb167441ab851c108dc2" # manifest list digest (multi-arch)
+      tag: "v0.12.1" ## if both tag and digest are omitted, defaults to the chart appVersion
+      digest: "sha256:92151fa5789abeb9cc6b21688326ee33f8b9adaceec0d44f3f604ef8aa7c2566" # manifest list digest (multi-arch)
     ## agentImage: is the image used for the agent container. This image is the default for this install, but can be overridden in the CR at package level.
     agent:
       repository: nvcr.io/nvidia/skyhook/agent

docs/kubernetes-support.md

@@ -2,15 +2,22 @@
 
 This document outlines Skyhook's approach to supporting different Kubernetes versions.
 
-## Current Support Matrix
+## What Version Should I Use?
 
-| Kubernetes Version | Skyhook Version | Status | Notes |
-|--------------------|-----------------|---------|-------|
-| 1.35, 1.34, 1.33, 1.32, 1.31  | v0.11.0+         | ✅ Fully Supported | Current stable versions |
-| 1.34, 1.33, 1.32, 1.31  | 0.10.x        | ✅ Fully Supported | Use v0.11.x  |
-| 1.34, 1.33, 1.32, 1.31  | v0.9.x       | ✅ Fully Supported |  |
-| 1.30               | v0.8.x          | ⚠️ Use older Skyhook | K8s 1.30 EOL: June 28, 2025 |
-| 1.29 and older    | v0.8.x or older | ⚠️ Use older Skyhook | No longer maintained |
+| Kubernetes Version | Recommended Skyhook | Status |
+|--------------------|---------------------|--------|
+| 1.35, 1.34, 1.33, 1.32, 1.31 | v0.12.x (latest) | ✅ Fully Supported, CI tested |
+| 1.30 and older | v0.8.x | ⚠️ Legacy (K8s 1.30 EOL June 2025) |
+
+### Previous Release Compatibility
+
+| Skyhook Version | Supported Kubernetes Versions |
+|-----------------|-------------------------------|
+| v0.12.x | 1.31, 1.32, 1.33, 1.34, 1.35 |
+| v0.11.x | 1.31, 1.32, 1.33, 1.34, 1.35 |
+| v0.10.x | 1.31, 1.32, 1.33, 1.34 |
+| v0.9.x  | 1.31, 1.32, 1.33, 1.34 |
+| v0.8.x  | 1.30 |
 
 ## Support Policy
 
@@ -59,21 +66,21 @@ We understand many installations run slightly older Kubernetes versions. Our str
 
 **Choose your Skyhook version based on your Kubernetes version:**
 
-- **Kubernetes 1.34, 1.33, 1.32, or 1.31:** Use latest Skyhook (v0.9.x or v0.10.0)
+- **Kubernetes 1.35, 1.34, 1.33, 1.32, or 1.31:** Use latest Skyhook (v0.12.x)
 - **Kubernetes 1.30:** Use Skyhook v0.8.x (K8s 1.30 is EOL but v0.8.x still works)
 - **Kubernetes 1.29 or older:** Use Skyhook v0.8.x or older (check release notes for compatibility)
 
 ### Migration Path
 
 **If you're on an older Kubernetes version:**
-1. **First:** Upgrade your Kubernetes cluster to a supported version (1.31, 1.32, 1.33, or 1.34)
+1. **First:** Upgrade your Kubernetes cluster to a supported version (1.31, 1.32, 1.33, 1.34, or 1.35)
 2. **Then:** Upgrade to the latest Skyhook version
 
 **If you're on Kubernetes 1.30:**
-- **Option A:** Upgrade to K8s 1.31/1.32/1.33/1.34, then use latest Skyhook
+- **Option A:** Upgrade to K8s 1.31/1.32/1.33/1.34/1.35, then use latest Skyhook
 - **Option B:** Stay on Skyhook v0.8.x until you can upgrade Kubernetes
 
-**Recommended:** If you can choose your Kubernetes version, use 1.34, 1.33, or 1.32 for the longest support runway.
+**Recommended:** If you can choose your Kubernetes version, use 1.35, 1.34, or 1.33 for the longest support runway.
 
 ## FAQ
 
@@ -104,7 +111,7 @@ Waiting 4+ weeks lets the ecosystem stabilize and gives us confidence in support
 ### How do you test compatibility?
 
 For each Skyhook release, we test against all supported Kubernetes versions using:
-- GitHub Actions matrix builds with multiple K8s versions (currently 1.31, 1.32, 1.33, 1.34)
+- GitHub Actions matrix builds with multiple K8s versions (currently 1.31, 1.32, 1.33, 1.34, 1.35)
 - Local testing with [kind](https://kind.sigs.k8s.io/)
 - Basic functionality and integration tests