pjfanning opened a new pull request, #801:
URL: https://github.com/apache/pekko-management/pull/801

   https://github.com/akka/akka-management/releases/tag/v1.4.1
   
   Now available under Apache License, version 2.0
   
   Ports the following akka-management PRs to pekko, adjusting package names 
and configuration keys accordingly:
   
   - **PR #1150** ([ci: fix flaky RU kubernetes 
test](https://github.com/akka/akka-management/pull/1150)): Already applied in 
pekko — skipped.
   - **PR #1151** ([docs: fix AppVersionRevision 
docs](https://github.com/akka/akka-management/pull/1151)): Fix wording in 
`rolling-updates.md` — change "for rolling updates that you define an 
increasing" to "to define an increasing", and fix trailing colon to period.
   - **PR #1152** ([fix: prevent extensions to fail with cyclic 
initialization](https://github.com/akka/akka-management/pull/1152)): Extensions 
were calling `ClusterBootstrap(system).start()` / 
`AppVersionRevision(system).start()` / `PodDeletionCost(system).start()` inside 
their own constructors which causes a cyclic re-initialization. Changed to call 
`start()` directly.
   - **PR #1153** ([doc: Clarify KUBERNETES_POD_NAME and KUBERNETES_NAMESPACE 
env variables](https://github.com/akka/akka-management/pull/1153)): Added 
`pod-namespace = ${?KUBERNETES_NAMESPACE}` to `discovery-kubernetes-api` 
reference.conf; added YAML examples for `KUBERNETES_POD_NAME` and 
`KUBERNETES_NAMESPACE` in both `rolling-updates.md` and 
`bootstrap/kubernetes-api.md`.
   - **PR #1155** ([fix: ensure versionPromise always 
completes](https://github.com/akka/akka-management/pull/1155)): Restructured 
`AppVersionRevision.start()` so the `versionPromise` is always completed 
(succeeds or fails) rather than being left pending when pod-name is not 
configured. Added `MissingPodNameException`. Refactored 
`AppVersionRevisionSpec` into a simple spec for the missing pod-name case, and 
moved all WireMock-based tests into the new `KubernetesApiSpec`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to