Fix broken links to k8s docs

docs/src/main/paradox/discovery/kubernetes.md

@@ -118,7 +118,7 @@ spec:
 
 ### Role-Based Access Control
 
-If your Kubernetes cluster has [Role-Based Access Control (RBAC)](https://kubernetes.io/docs/admin/authorization/rbac/)
+If your Kubernetes cluster has [Role-Based Access Control (RBAC)](https://kubernetes.io/docs/reference/access-authn-authz/rbac/)
 enabled, you'll also have to grant the Service Account that your pods run under access to list pods. The following
 configuration can be used as a starting point. It creates a `Role`, `pod-reader`, which grants access to query pod
 information. It then binds the default Service Account to the `Role` by creating a `RoleBinding`.

docs/src/main/paradox/kubernetes-deployment/preparing-for-production.md

@@ -66,7 +66,7 @@ spec:
 Here are a few things to note:
 
 * We're using a Kubernetes deployment. Deployments are logical groupings of pods that represent a single service using the same template. 
-  They support [configurable rolling updates](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.11/#deploymentstrategy-v1-apps), 
+  They support configurable rolling updates, 
   meaning the cluster will be gradually upgraded, rather than upgrading every node at once and incurring an outage. Be sure to consult @ref:[Kubernetes Rolling Updates](../rolling-updates.md#kubernetes-rolling-updates) for recommendations.
 * We label the pod in the `template` with `app: appka`. This must match the ActorSystem name so that @ref[Akka Bootstrap](../bootstrap/index.md) finds the other nodes in the cluster.
 * The image we're using is `akka-sample-cluster-kubernetes:latest`. This corresponds to the name and version of the service in our build.