Add release-1.18 reference to documentation

Signed-off-by: Sascha Grunert <sgrunert@suse.com>

Author: saschagrunert

README.md

@@ -22,6 +22,7 @@ CRI-O and Kubernetes follow the same release cycle and deprecation policy. For m
 | CRI-O 1.15.x  - release-1.15 | Kubernetes 1.15 branch, v1.15.x | =                  |
 | CRI-O 1.16.x  - release-1.16 | Kubernetes 1.16 branch, v1.16.x | =                  |
 | CRI-O 1.17.x  - release-1.17 | Kubernetes 1.17 branch, v1.17.x | =                  |
+| CRI-O 1.18.x  - release-1.18 | Kubernetes 1.18 branch, v1.18.x | =                  |
 | CRI-O HEAD    - master       | Kubernetes master branch        | ✓                  |
 
 Key:

contrib/test/integration/main.yml

@@ -25,7 +25,7 @@
     - name: clone build and install kubernetes
       include: "build/kubernetes.yml"
       vars:
-        k8s_git_version: "release-1.17"
+        k8s_git_version: "release-1.18"
         k8s_github_fork: "kubernetes"
         crio_socket: "/var/run/crio/crio.sock"
       when: "(cgroupv2 is undefined) or (cgroupv2 == False) | bool"

tutorials/setup.md

@@ -170,7 +170,7 @@ cd cri-o
 
 Make sure your `CRI-O` and `kubernetes` versions are of matching major versions.
 For instance, if you want to be compatible with the latest kubernetes release,
-you'll need to use the latest tagged release of `CRI-O` on branch `release-1.17`.
+you'll need to use the latest tagged release of `CRI-O` on branch `release-1.18`.
 
 ## Build