async-container 0.23.0 → 0.23.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 83778c10be3ccd8ed8b61d607d5e742f2b727f01a2ee16149cf298a70585a083
-  data.tar.gz: 14eb47ac328d93b39517b74210f6a4d26b22afa13aefa42df105e2d9e55d16b1
+  metadata.gz: 45498b6ccc16a193e4562b68437909aa982613b11a3959608de293246edc1f31
+  data.tar.gz: fa3b269ba5e24b5500fb05409a6c5835127adf8cbda92bff54cc661358e10921
 SHA512:
-  metadata.gz: fc053221b626ecfbec43f512442547d151737dc8894efb15a4ab53e9f651d5597162206dd1260c43a6d5a0599d39edb2bd37cb21ab0a3c415ee44b9f42b68117
-  data.tar.gz: 36ae31abb21e0ee9bc7db47fc881de4ba2ddd3b0aa13b8878ae639cf96e8c56b0bfb561cb34074ee2d10b65e8bcdb5bd4e678d48a7bf1d9527774a525d43eb98
+  metadata.gz: 4481f2950cfacc074c010419ce3afaa785435df9066b072e4d514a7ea3319fd930242afb8ef0f3e40020d7674209d792a4a42059f1f44cdc3270669bca52ef7b
+  data.tar.gz: '018f892e9b7b9cd7703ce0b9e15a8eb689804563b8d691a676f51a0ad79b0d78681d34bca2c63da9e508c8b48dc617cb03dde3911af5271e42997a334dcf06bd'

data/lib/async/container/controller.rb

@@ -149,7 +149,7 @@ module Async
 					old_container&.stop(@graceful_stop)
 				end
 				
-				@notify&.ready!
+				@notify&.ready!(size: @container.size)
 			ensure
 				# If we are leaving this function with an exception, try to kill the container:
 				container&.stop(false)
@@ -185,7 +185,7 @@ module Async
 			
 			# Enter the controller run loop, trapping `SIGINT` and `SIGTERM`.
 			def run
-				@notify&.status!("Initializing...")
+				@notify&.status!("Initializing controller...")
 				
 				with_signal_handlers do
 					self.start

data/lib/async/container/generic.rb

@@ -51,6 +51,11 @@ module Async
 			# @attribute [Group] The group of running children instances.
 			attr :group
 			
+			# @returns [Integer] The number of running children instances.
+			def size
+				@group.size
+			end
+			
 			# @attribute [Hash(Child, Hash)] The state of each child instance.
 			attr :state
 			

data/lib/async/container/group.rb

@@ -32,6 +32,11 @@ module Async
 			# @attribute [Hash(IO, Fiber)] the running tasks, indexed by IO.
 			attr :running
 			
+			# @returns [Integer] The number of running processes.
+			def size
+				@running.size
+			end
+			
 			# Whether the group contains any running processes.
 			# @returns [Boolean]
 			def running?
@@ -175,7 +180,8 @@ module Async
 			protected
 			
 			def wait_for_children(duration = nil)
-				Console.debug(self, "Waiting for children...", duration: duration, running: @running)
+				# This log is a big noisy and doesn't really provide a lot of useful information.
+				# Console.debug(self, "Waiting for children...", duration: duration, running: @running)
 				
 				if !@running.empty?
 					# Maybe consider using a proper event loop here:

data/lib/async/container/version.rb

@@ -5,6 +5,6 @@
 
 module Async
 	module Container
-		VERSION = "0.23.0"
+		VERSION = "0.23.1"
 	end
 end

data/readme.md

@@ -22,6 +22,10 @@ Please see the [project documentation](https://socketry.github.io/async-containe
 
 Please see the [project releases](https://socketry.github.io/async-container/releases/index) for all releases.
 
+### v0.23.0
+
+  - [Add support for `NOTIFY_LOG` for Kubernetes readiness probes.](https://socketry.github.io/async-container/releases/index#add-support-for-notify_log-for-kubernetes-readiness-probes.)
+
 ### v0.21.0
 
   - Use `SIGKILL`/`Thread#kill` when the health check fails. In some cases, `SIGTERM` may not be sufficient to terminate a process because the signal can be ignored or the process may be in an uninterruptible state.

data/releases.md

@@ -1,5 +1,26 @@
 # Releases
 
+## v0.23.0
+
+### Add support for `NOTIFY_LOG` for Kubernetes readiness probes.
+
+You may specify a `NOTIFY_LOG` environment variable to enable readiness logging to a log file. This can be used for Kubernetes readiness probes, e.g.
+
+``` yaml
+containers:
+	- name: falcon
+		env:
+			- name: NOTIFY_LOG
+				value: "/tmp/notify.log"
+		command: ["falcon", "host"]
+		readinessProbe:
+			exec:
+				command: ["sh", "-c", "grep -q '\"ready\":true' /tmp/notify.log"]
+			initialDelaySeconds: 5
+			periodSeconds: 5
+			failureThreshold: 12
+```
+
 ## v0.21.0
 
   - Use `SIGKILL`/`Thread#kill` when the health check fails. In some cases, `SIGTERM` may not be sufficient to terminate a process because the signal can be ignored or the process may be in an uninterruptible state.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: async-container
 version: !ruby/object:Gem::Version
-  version: 0.23.0
+  version: 0.23.1
 platform: ruby
 authors:
 - Samuel Williams