Bump chart versions to 4.1.1 across all components

[ilijabojanovic]

Description

Bump charts to 4.1.1 to have proper operator version

Related Issue

Motivation and Context

Test Coverage For This Change

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Refactoring or add test (improvements in base code or adds test coverage to functionality)
• Documentation updates or improvements.

Checklist

• Make sure you are requesting to pull a topic/feature/bugfix branch (right side). If PRing from your fork, don't come from your master!
• Make sure you are making a pull request against our master branch (left side). Also, it would be best if you started your change off our latest master.
• My change requires a change to the documentation.
  • I have manually updated the README(s)/documentation accordingly.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[probelabs]

This pull request bumps the version of all Helm charts from 4.1.0 to 4.1.1 and updates the Kubernetes version in the CI test environment.

Files Changed Analysis

The changes are consistently applied across all component and umbrella charts:

• Chart.yaml files (10 files): The version field is updated to 4.1.1.
• Chart.lock files (4 files): Dependency versions are updated to 4.1.1, and file digests are regenerated.
• .github/workflows/run-tests.yaml: The kind node image is updated from kindest/node:v1.29.1 to kindest/node:v1.34.0.

Architecture & Impact Assessment

• What this PR accomplishes: It aligns the versions of all Helm charts in the repository to 4.1.1 for a new release and modernizes the CI testing environment.
• Key technical changes introduced:
  • Widespread version bump across all Helm charts.
  • Upgrade of the Kubernetes version used in the kind cluster for CI tests.
• Affected system components: The change impacts the packaging, versioning, and CI process for all Helm charts. There are no direct changes to the runtime behavior of the deployed Tyk components.

Component Dependencies

The following diagram shows the relationship between the umbrella charts and the updated component charts.

graph TD
    subgraph Umbrella Charts
        A[tyk-stack]
        B[tyk-control-plane]
        C[tyk-data-plane]
        D[tyk-oss]
    end

    subgraph Component Charts
        C1[tyk-bootstrap]
        C2[tyk-dashboard]
        C3[tyk-dev-portal]
        C4[tyk-gateway]
        C5[tyk-mdcb]
        C6[tyk-pump]
    end

    A --> C1 & C2 & C3 & C4 & C6
    B --> C1 & C2 & C3 & C4 & C5 & C6
    C --> C4 & C6
    D --> C4 & C6

Loading

Scope Discovery & Context Expansion

The scope is limited to updating Helm chart metadata and a single CI workflow file. While the changes themselves are straightforward, the update to the kind node image in run-tests.yaml to v1.34.0 is a significant jump and may warrant verification that it's the intended version. No further code exploration is necessary to understand the direct impact of this PR.

Metadata

• Review Effort: 1 / 5
• Primary Label: chore

---

Powered by Visor from Probelabs

Last updated: 2025-12-11T17:36:56.414Z | Triggered by: pr_updated | Commit: 31ee467

💡 TIP: You can chat with Visor using /visor ask <your question>

[probelabs]

Security Issues (1)

Severity	Location	Issue
🟡 Warning	.github/workflows/run-tests.yaml:135	The `kindest/node` image version `v1.34.0` appears to be invalid or a typo. The latest stable Kubernetes version is significantly lower. Using a non-existent or incorrect image tag can break the CI/CD pipeline. In a worst-case scenario, if a malicious image exists at this tag (typosquatting), it could lead to a supply chain attack by running compromised code in the CI environment. 💡 Suggestion Verify the intended Kubernetes version and update the `node_image` to a valid, stable, and officially supported version. For example, if upgrading, use a recent version like `v1.30.0` or the latest supported by the `helm/kind-action`. If this was a typo for `v1.24.0`, please correct it. 🔧 Suggested Fix node_image: "kindest/node:v1.30.0"

Architecture Issues (1)

Severity	Location	Issue
🟠 Error	.github/workflows/run-tests.yaml:135	The `kindest/node` image version `v1.34.0` specified for the kind cluster does not exist. This will cause the 'run-tests' workflow to fail when it attempts to pull the container image. The `kindest/node` image tags correspond to Kubernetes versions, and v1.34.0 is not a released version. 💡 Suggestion Update the `node_image` to a valid and available version from Docker Hub. If the intent was to upgrade Kubernetes, choose a recent, stable, and existing version (e.g., `v1.29.2`). If this change was a mistake, revert it to the previous version (`v1.29.1`).

✅ Performance Check Passed

No performance issues found – changes LGTM.

Quality Issues (1)

Severity	Location	Issue
🟠 Error	.github/workflows/run-tests.yaml:135	The specified kind node image `kindest/node:v1.34.0` corresponds to Kubernetes v1.34.0, which is not a released version. This will cause the CI test setup to fail when creating the kind cluster. 💡 Suggestion Please use a valid and existing kind node image tag. The latest stable Kubernetes version is v1.30.0, so `kindest/node:v1.30.0` might be what was intended. Please verify the target Kubernetes version for testing and correct the image tag.

---

Powered by Visor from Probelabs

Last updated: 2025-12-11T17:36:59.430Z | Triggered by: pr_updated | Commit: 31ee467

💡 TIP: You can chat with Visor using /visor ask <your question>

[github-actions]

🚨 Jira Linter Failed

Commit: 31ee467
Failed at: 2025-12-11 17:36:06 UTC

The Jira linter failed to validate your PR. Please check the error details below:

🔍 Click to view error details

failed to validate branch and PR title rules: branch name 'release-4.1.1' must contain a valid Jira ticket ID (e.g., ABC-123)

Next Steps

• Ensure your branch name contains a valid Jira ticket ID (e.g., ABC-123)
• Verify your PR title matches the branch's Jira ticket ID
• Check that the Jira ticket exists and is accessible

---

This comment will be automatically deleted once the linter passes.