From 8a70e290e22bc410b867ca289a31b91f30a9d910 Mon Sep 17 00:00:00 2001 From: buildmaster Date: Thu, 10 Dec 2020 11:49:16 +0000 Subject: [PATCH] Bumping versions --- README.adoc | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/README.adoc b/README.adoc index 2af48f0c..853cfc7c 100644 --- a/README.adoc +++ b/README.adoc @@ -83,9 +83,6 @@ Secret changes. spring-cloud-starter-kubernetes-client-all ---- -| All Spring Cloud Kubernetes features. - -|=== == DiscoveryClient for Kubernetes @@ -98,6 +95,7 @@ access from a Spring Boot application running as a pod. This is something that you get for free by adding the following dependency inside your project: ==== +Fabric8 Kubernetes Client [source,xml] ---- @@ -107,6 +105,17 @@ This is something that you get for free by adding the following dependency insid ---- ==== +==== +Kubernetes Java Client +[source,xml] +---- + + org.springframework.cloud + spring-cloud-starter-kubernetes-client + +---- +==== + To enable loading of the `DiscoveryClient`, add `@EnableDiscoveryClient` to the according configuration or application class, as the following example shows: ==== @@ -878,6 +887,12 @@ Depending on the requirements, you'll need `get`, `list` and `watch` permission |spring-cloud-starter-kubernetes-fabric8-config |configmaps, secrets + +|spring-cloud-starter-kubernetes-client +|pods, services, endpoints + +|spring-cloud-starter-kubernetes-client-config +|configmaps, secrets |=== For development purposes, you can add `cluster-reader` permissions to your `default` service account. On a production system you'll likely want to provide more granular permissions.