diff --git a/docs/src/main/paradox/discovery/kubernetes.md b/docs/src/main/paradox/discovery/kubernetes.md index fc61a7aa..e293c440 100644 --- a/docs/src/main/paradox/discovery/kubernetes.md +++ b/docs/src/main/paradox/discovery/kubernetes.md @@ -110,7 +110,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`. diff --git a/docs/src/main/paradox/kubernetes-deployment/building-using-maven.md b/docs/src/main/paradox/kubernetes-deployment/building-using-maven.md index a8b012f8..0a6a4ad4 100644 --- a/docs/src/main/paradox/kubernetes-deployment/building-using-maven.md +++ b/docs/src/main/paradox/kubernetes-deployment/building-using-maven.md @@ -99,7 +99,7 @@ To build and publish the image run the following. The Docker username and regist Note that the registry to push to must include the username, for example `-Ddocker.registry=docker.io/youruser`. -Security information (i.e. user and password) can be specified in multiple ways as described in section [docker-maven-plugin authentication](http://dmp.fabric8.io/#authentication). +Security information (i.e. user and password) can be specified in multiple ways as described in section [docker-maven-plugin authentication](https://dmp.fabric8.io/#authentication). ``` mvn -Ddocker.username= -Ddocker.registry=/ package docker:push diff --git a/docs/src/main/paradox/kubernetes-deployment/deploying.md b/docs/src/main/paradox/kubernetes-deployment/deploying.md index e825c845..8eac4790 100644 --- a/docs/src/main/paradox/kubernetes-deployment/deploying.md +++ b/docs/src/main/paradox/kubernetes-deployment/deploying.md @@ -150,7 +150,7 @@ for 'hello world': kubectl expose deployment appka --type=LoadBalancer --name=appka-service -You can inspect the Pekko Cluster membership status with the [Cluster HTTP Management](https://doc.pekko.io/docs/pekko-management/current/cluster-http-management.html). +You can inspect the Pekko Cluster membership status with the @ref:[Cluster HTTP Management](../cluster-http-management.md). curl http://127.0.0.1:7626/cluster/members/ diff --git a/docs/src/main/paradox/kubernetes-deployment/preparing-for-production.md b/docs/src/main/paradox/kubernetes-deployment/preparing-for-production.md index 47a5673b..0f6f7f46 100644 --- a/docs/src/main/paradox/kubernetes-deployment/preparing-for-production.md +++ b/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](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/), meaning the cluster will be gradually upgraded, rather than upgrading every node at once and incurring an outage. * We label the pod in the `template` with `app: appka`. This must match the ActorSystem name so that @ref[Pekko Bootstrap](../bootstrap/index.md) finds the other nodes in the cluster. * The image we're using is `pekko-sample-cluster-kubernetes:latest`. This corresponds to the name and version of the service in our build. diff --git a/docs/src/main/paradox/loglevels/logback.md b/docs/src/main/paradox/loglevels/logback.md index f6ae94e0..aa9dafe9 100644 --- a/docs/src/main/paradox/loglevels/logback.md +++ b/docs/src/main/paradox/loglevels/logback.md @@ -6,7 +6,7 @@ Dynamic Log Levels for Logback hooks into Pekko Management and provides a route @@project-info{ projectId="management-loglevels-logback" } -Requires @ref:[Pekko Management](../pekko-management.md) and that the application uses [Logback](http://logback.qos.ch) as logging backend. +Requires @ref:[Pekko Management](../pekko-management.md) and that the application uses [Logback](https://logback.qos.ch) as logging backend. @@dependency[sbt,Gradle,Maven] { symbol1=PekkoManagementVersion diff --git a/integration-test/kubernetes-api-java/pom.xml b/integration-test/kubernetes-api-java/pom.xml index fa0dd0fd..f5f87dae 100644 --- a/integration-test/kubernetes-api-java/pom.xml +++ b/integration-test/kubernetes-api-java/pom.xml @@ -19,7 +19,7 @@ 1.8 UTF-8 1.0.1 - 1.0.0-RC2 + 1.0.0 0.0.0 2.13 diff --git a/project/Dependencies.scala b/project/Dependencies.scala index e0eb4a17..b63f6890 100644 --- a/project/Dependencies.scala +++ b/project/Dependencies.scala @@ -19,7 +19,7 @@ object Dependencies { // Align the versions in integration-test/kubernetes-api-java/pom.xml val pekkoVersion = "1.0.1" - val pekkoHttpVersion = "1.0.0-RC2" + val pekkoHttpVersion = "1.0.0" val scalaTestVersion = "3.2.14" val scalaTestPlusJUnitVersion = scalaTestVersion + ".0" diff --git a/scripts/link-validator.conf b/scripts/link-validator.conf index 25fb3dbd..5c1ed883 100644 --- a/scripts/link-validator.conf +++ b/scripts/link-validator.conf @@ -29,6 +29,8 @@ site-link-validator { // e.g. "^api/alpakka/snapshot/pekko/stream/alpakka/googlecloud/storage/impl/Formats.*" ignore-prefixes = [ + # example in docs + "http://127.0.0.1" # Fails after a number of requests with "403 Forbidden" "https://javadoc.io/static/" # GitHub will block with "429 Too Many Requests" @@ -36,12 +38,49 @@ site-link-validator { # Github links generated by sbt-license-report "http://github.com/" # Other links generated by sbt-license-report - + "http://asm.objectweb.org/" + "http://groovy.codehaus.org/" + "http://www.mockito.org" + "https://glassfish.dev.java.net/nonav/public/CDDL+GPL.html" # Occasionally returns a 500 Internal Server Error "http://code.google.com/" ] non-https-whitelist = [ + # license report + "http://ant.apache.org/" + "http://asm.objectweb.org/" + "http://asm.ow2.io/" + "http://commons.apache.org/" + "http://ezmorph.sourceforge.net" + "http://findbugs.sourceforge.net/" + "http://groovy.codehaus.org/modules/http-builder/" + "http://hamcrest.org/JavaHamcrest/" + "http://hc.apache.org/" + "http://jopt-simple.github.io/jopt-simple" + "http://json-lib.sourceforge.net" + "http://junit.org" + "http://maven.apache.org" + "http://nekohtml.sourceforge.net/" + "http://opensource.org/" + "http://parboiled.org" + "http://servlet-spec.java.net" + "http://wiremock.org" + "http://www.apache.org/license/" + "http://www.apache.org/licenses/" + "http://www.eclipse.org/legal/epl-v10.html" + "http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html" + "http://www.jetbrains.org" + "http://www.joda.org/joda-time/" + "http://www.mockito.org" + "http://www.opensource.org/licenses/bsd-license.php" + "http://www.opensource.org/licenses/mit-license.php" + "http://www.reactive-streams.org/" + "http://www.scala-lang.org/" + "http://www.scalatest.org" + "http://www.slf4j.org" + "http://xerces.apache.org/xerces2-j" + "http://xml.apache.org/" ] }