From f0da505f7bb3b6ce3e244e639881cdd14cb5281a Mon Sep 17 00:00:00 2001 From: Auri Munoz Date: Tue, 28 Nov 2023 15:11:21 +0100 Subject: [PATCH] Add the good format for a list --- _posts/2023-11-23-stork-latest-news.adoc | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/_posts/2023-11-23-stork-latest-news.adoc b/_posts/2023-11-23-stork-latest-news.adoc index 12114e907a5..5bb0b1e0cbc 100644 --- a/_posts/2023-11-23-stork-latest-news.adoc +++ b/_posts/2023-11-23-stork-latest-news.adoc @@ -127,9 +127,10 @@ This enhancement was driven by the specific requirements of Kubernetes service d problems. So, out of the box, Stork Kubernetes service discovery now comes with a tailored cache expiration strategy to keep service instances until an event occurs. If you would like to do so for your custom service discovery implementations, you need: -- Extend the CachingServiceDiscovery as mentioned above. -- Implement the `cache` method where the expiration strategy is defined. -- Invalidate the cache when the expiration condition evaluates to `true`. + +* Extend the CachingServiceDiscovery as mentioned above. +* Implement the `cache` method where the expiration strategy is defined. +* Invalidate the cache when the expiration condition evaluates to `true`. Look at the example bellow: