Update CronJob and PodDisruptionBudget apiVersion for K8s 1.25 (#1658)

* Update CronJob apiVersion.
Update PodDisruptionBudget apiVersion

Signed-off-by: Manuel Fontan <[email protected]>

* code review: remove k8s 1.20 api tests

Signed-off-by: Manuel Fontan <[email protected]>

Author: manfontan

.github/workflows/pull_request.yml

@@ -39,7 +39,7 @@ jobs:
       matrix:
         # With a new supported Kubernetes version we should adjust the version
         # See https://kubernetes.io/releases for the current releases
-        kubever: [ "v1.20.0", "v1.21.1", "v1.22.0", "v1.23.0" ]
+        kubever: [ "v1.21.1", "v1.22.0", "v1.23.0" ]
     steps:
     - name: Set up Go
       uses: actions/setup-go@v1

config/samples/pod_disruption_budget.yaml

@@ -1,6 +1,6 @@
 # Kubernetes won't deliberately cause an interruption to a ready storage pod if
 # that would drop the ready count below 5.
-apiVersion: policy/v1beta1
+apiVersion: policy/v1
 kind: PodDisruptionBudget
 metadata:
   name: sample-cluster-storage
@@ -12,7 +12,7 @@ spec:
       fdb-cluster-name: sample-cluster
       fdb-process-class: storage
 ---
-apiVersion: policy/v1beta1
+apiVersion: policy/v1
 kind: PodDisruptionBudget
 metadata:
   name: sample-cluster-log
@@ -24,7 +24,7 @@ spec:
       fdb-cluster-name: sample-cluster
       fdb-process-class: log
 ---
-apiVersion: policy/v1beta1
+apiVersion: policy/v1
 kind: PodDisruptionBudget
 metadata:
   name: sample-cluster-transaction

docs/manual/getting_started.md

@@ -52,7 +52,7 @@ By default each pod will have two containers and one init container. The `founda
 Now that your cluster is deployed, you can easily access the cluster. As an example, we are going to deploy a [Kubernetes Job](https://kubernetes.io/docs/tasks/job/) that will check the status of the cluster every minute. The `cluster file` is available through the exposed `config map` that can be mounted as follows:
 
 ```yaml
-apiVersion: batch/v1beta1
+apiVersion: batch/v1
 kind: CronJob
 metadata:
   name: fdbcli-status-cronjob