1.0.x update local leader before notifications (#410)

* Fix leader election example

* Update local leader before sending events

spring-cloud-kubernetes-examples/kubernetes-leader-election-example/README.md

@@ -27,9 +27,17 @@ And finally, if the leadership is yielded or revoked for some reason, the old le
 
 ## Example application usage
 
-To begin with, build and deploy the application:
+Leader election mechanism uses Kubernetes ConfigMap feature to coordinate leadership information.
+To access ConfigMap user needs correct role and role binding.
+Create them using the following commands:
 ```
-mvn clean package fabric8:deploy -Pkubernetes
+kubectl apply -f leader-role.yml
+kubectl apply -f leader-rolebinding.yml
+```
+
+Now build and deploy the application:
+```
+mvn clean fabric8:deploy -Pkubernetes
 ```
 
 This will deploy a single application instance to the cluster and that instance will automatically become a leader.
@@ -76,8 +84,4 @@ Thus, when trying to yield the leadership, request might go to a non-leader node
 
 > Note: instances periodically try to acquire leadership and Spring Cloud Kubernetes doesn't decide which one of them is more worth to become one.
 Thus, it is possible that the instance which just yielded the leadership, made another leadership take over request faster than another instances and became a leader again.
-
-## Access control notice 
-
-Leader election mechanism uses Kubernetes ConfigMap feature to coordinate leadership information.
-In order to access it, [Role](./src/main/fabric8/role.yaml) and [RoleBinding](./src/main/fabric8/rb.yaml) objects are defined. 
+ 

spring-cloud-kubernetes-examples/kubernetes-leader-election-example/leader-role.yml

@@ -0,0 +1,15 @@
+apiVersion: rbac.authorization.k8s.io/v1
+kind: Role
+metadata:
+  name: leader
+  labels:
+    app: kubernetes-leader-election-example
+    group: org.springframework.cloud
+rules:
+- apiGroups:
+  - ""
+  resources:
+  - pods
+  - configmaps
+  verbs:
+  - '*'

spring-cloud-kubernetes-examples/kubernetes-leader-election-example/leader-rolebinding.yml

@@ -0,0 +1,15 @@
+apiVersion: rbac.authorization.k8s.io/v1
+kind: RoleBinding
+metadata:
+  labels:
+    app: kubernetes-leader-election-example
+    group: org.springframework.cloud
+  name: leader
+roleRef:
+  apiGroup: ""
+  kind: Role
+  name: leader
+subjects:
+- kind: ServiceAccount
+  name: default
+  apiGroup: ""

spring-cloud-kubernetes-examples/kubernetes-leader-election-example/pom.xml

@@ -36,6 +36,10 @@
 			<groupId>org.springframework.boot</groupId>
 			<artifactId>spring-boot-starter-web</artifactId>
 		</dependency>
+		<dependency>
+			<groupId>org.springframework.boot</groupId>
+			<artifactId>spring-boot-starter-actuator</artifactId>
+		</dependency>
 		<dependency>
 			<groupId>org.springframework.cloud</groupId>
 			<artifactId>spring-cloud-kubernetes-leader</artifactId>

spring-cloud-kubernetes-examples/kubernetes-leader-election-example/src/main/fabric8/rb.yaml

@@ -1,13 +0,0 @@
-apiVersion: rbac.authorization.k8s.io/v1beta1
-kind: RoleBinding
-metadata:
-  name: leader
-  namespace: default
-roleRef:
-  apiGroup: rbac.authorization.k8s.io
-  kind: Role
-  name: leader
-subjects:
-  - kind: ServiceAccount
-    name: default
-    namespace: default

spring-cloud-kubernetes-examples/kubernetes-leader-election-example/src/main/fabric8/role.yaml

@@ -1,12 +0,0 @@
-apiVersion: rbac.authorization.k8s.io/v1beta1
-kind: Role
-metadata:
-  name: leader
-  namespace: default
-rules:
-  - apiGroups:
-    resources:
-      - pods
-      - configmaps
-    verbs:
-      - "*"