Merge pull request #92 from akash4sh/main

updated traefik chart

charts/traefik/Chart.yaml

@@ -1,17 +1,18 @@
 annotations:
   artifacthub.io/changes: |
-    - "✨ update chart to version 20.8.0"
+    - "✨ update chart to version 24.0.0"
     - "✨ add support for default entrypoints"
     - "✨ add support for OpenTelemetry and Traefik v3"
 apiVersion: v2
-appVersion: v2.9.6
+appVersion: v2.10.4
 description: A Traefik based Kubernetes ingress controller
 home: https://traefik.io/
 icon: https://raw.githubusercontent.com/traefik/traefik/v2.3/docs/content/assets/img/traefik.logo.png
 keywords:
 - traefik
 - ingress
 - networking
+kubeVersion: '>=1.16.0-0'
 maintainers:
 - email: [email protected]
   name: emilevauge
@@ -28,4 +29,4 @@ sources:
 - https://github.com/traefik/traefik
 - https://github.com/traefik/traefik-helm-chart
 type: application
-version: 2.0.0
+version: 1.0.1

charts/traefik/Guidelines.md

@@ -2,27 +2,30 @@
 
 This document outlines the guidelines for developing, managing and extending the Traefik helm chart.
 
+This Helm Chart is documented using field description from comments with [helm-docs](https://github.com/norwoodj/helm-docs).
+
 Optionallity
 All non-critical features (Features not mandatory to starting Traefik) in the helm chart must be optional. All non-critical features should be disabled (commented out) in the values.yaml file. All optional non-critical features should be disabled (commented out) in the values.yaml file, and have a comment # (Optional) in the line above. This allows minimal configuration, and ease of extension.
 
-## Critical Feature Example
+## Feature Example
 
 ```yaml
 image:
-  name: traefik
+  # -- Traefik image host registry
+  registry: docker.io
 ```
 
-This feature is critical, and therefore is defined clearly in the values.yaml file.
+This feature is expected and therefore is defined clearly in the values.yaml file.
 
-## Non-Critical Feature Example
+## Optional Feature Example
 
 ```yaml
 # storage:
 #   controlNode:
 #     type: emptyDir
 ```
 
-This feature is non-critical, and therefore is commented out by default in the values.yaml file.
+This feature is optional, non-critical, and therefore is commented out by default in the values.yaml file.
 
 To allow this, template blocks that use this need to recursively test for existence of values before using them:
 
@@ -87,7 +90,3 @@ There should be an empty commented line between each primary key in the values.y
 ## Values YAML Design
 
 The values.yaml file is designed to be user-friendly. It does not have to resemble the templated configuration if it is not conducive. Similarly, value names to not have to correspond to fields in the tempate if it is not condusive.
-
-## Comments
-
-The values.yaml file should not contain comments or explainations of what options are, or what values are available. The values table in the README file is for this purpose.

charts/traefik/README.md

@@ -8,6 +8,10 @@ microservices with ease.
 This chart bootstraps Traefik version 2 as a Kubernetes ingress controller,
 using Custom Resources `IngressRoute`: <https://docs.traefik.io/providers/kubernetes-crd/>.
 
+It's now possible to use this chart with Traefik v3 (current tested with beta3).
+Helm will auto detect which version is used based on image.tag. Set image.tag to a semver higher than 3.0, e.g. "v3.0.0-beta3".
+See [Migration guide from v2 to v3](https://doc.traefik.io/traefik/v3.0/migration/v2-to-v3/) and upgrading section of this chart on CRDs.
+
 ### Philosophy
 
 The Traefik HelmChart is focused on Traefik deployment configuration.
@@ -36,7 +40,8 @@ Due to changes in CRD version support, the following versions of the chart are u
 |                         |  Kubernetes v1.15 and below | Kubernetes v1.16-v1.21 | Kubernetes v1.22 and above |
 |-------------------------|-----------------------------|------------------------|----------------------------|
 | Chart v9.20.2 and below | [x]                         | [x]                    |                            |
-| Chart 10.0.0 and above  |                             | [x]                    | [x]                        |
+| Chart v10.0.0 and above |                             | [x]                    | [x]                        |
+| Chart v22.0.0 and above |                             |                        | [x]                        |
 
 ### Deploying Traefik
 
@@ -70,12 +75,18 @@ New major version indicates that there is an incompatible breaking change.
 
 ### Upgrading CRDs
 
+🛂 **Warning**: Traefik v3 totally removes the crd support for traefik.containo.us CRDs. By default this helm installs the CRDs compatible with v2 also, but Traefik v3 will no longer monitor them. There is no support for deprecation errors, so your existing resources may silently fail to work after upgrade to Traefik v3. See [Migration guide from v2 to v3](https://doc.traefik.io/traefik/v3.0/migration/v2-to-v3/) for more details.
+
 With Helm v3, CRDs created by this chart can not be updated, cf the [Helm Documentation on CRDs](https://helm.sh/docs/chart_best_practices/custom_resource_definitions). Please read carefully release notes of this chart before upgrading CRDs.
 
 ```bash
 kubectl apply --server-side --force-conflicts -k https://github.com/traefik/traefik-helm-chart/traefik/crds/
 ```
 
+### Upgrading after 18.X+
+
+It's detailed in [release notes](https://github.com/traefik/traefik-helm-chart/releases).
+
 ### Upgrading from 17.x to 18.x
 
 Since v18.x, this chart by default merges TCP and UDP ports into a single (LoadBalancer) `Service`.
@@ -116,3 +127,9 @@ This will override the new `Release.Name-Release.Namespace` pattern to avoid any
 ## Contributing
 
 If you want to contribute to this chart, please read the [Contributing Guide](./CONTRIBUTING.md).
+
+Thanks to all the people who have already contributed!
+
+<a href="https://github.com/traefik/traefik-helm-chart/graphs/contributors">
+  <img src="https://contributors-img.web.app/image?repo=traefik/traefik-helm-chart" />
+</a>