Update README for K3s Traefik version

Update K3s references to the default Traefik version it ships with as this is now 2.5.0.

README.md

@@ -38,17 +38,19 @@ Routes], which is what the configuration in this repository is based on.
 workloads from Rancher Labs. k3s installs Traefik as the Ingress Controller, and
 a service loadbalancer (klippy-lb) by default so that the cluster is ready to go
 as soon as it starts up. K3s previously installed Traefik 1.7, and more recently
-Traefik 2.5. The instructions below will be deploying a k3s cluster _without_
+Traefik 2.5.0. The instructions below will be deploying a k3s cluster _without_
 the default Traefik installation as we want to deploy this ourselves so that we
 can use the latest Traefik v2 release, version 2.5 at time of writing, and the
 Kubernetes Ingress Controller.
 
 ### k3s v1.21.0+k3s1
 
 The K3s `v1.21.0+k3s1` release includes core support for Traefik v2.4 instead of
-Traefik 1.7. This repository will continue to be maintained as:
+Traefik 1.7. This is now v2.5.0 in later K3s releases. This repository will
+however continue to be maintained as:
 
-- it uses Traefik 2.5 vs. 2.4
+- it attempts to remain on the latest Traefik releases, v2.5.6 at time of writing,
+  vs. 2.5.0
 - people will be on older releases of k3s for some time
 - it is not specific to k3s and should support other k8s distributions
 - it contains additional helpful configuration and examples than that provided
@@ -131,7 +133,7 @@ Comment out the below annotation in the `005-deployment.yaml` and
 
 ## Install Traefik Kubernetes CRD Ingress Controller
 
-k3s ships with Traefik 1.7 or Traefik 2.4 by default, depending on the release
+k3s ships with Traefik 1.7 or Traefik 2.5.0 by default, depending on the release
 version, so we need to install Traefik v2 separately using the manifests in this
 repository. The `--disable=traefik` argument used will mean that Traefik is not
 installed.