He-Pin opened a new pull request, #3276: URL: https://github.com/apache/pekko/pull/3276
### Motivation The rolling-updates docs explained the manual `pekko.cluster.app-version` setting but did not mention that Pekko Management can derive it automatically from a Kubernetes Deployment, so users on Kubernetes bumped the version by hand unnecessarily. ### Modification Add a paragraph to the rolling-updates page pointing to the **app-version from Deployment** feature in Pekko Management, which sets `app-version` from the Kubernetes `deployment.kubernetes.io/revision` annotation. The upstream commit also touched `deploying.md` and added a `#kubernetes-rolling-updates` anchor to an existing link in `rolling-updates.md`, but pekko's `deploying.md` has diverged (no matching "Rolling updates" section) and pekko's corresponding `rolling-updates.md` text was rewritten without that link, so only the new app-version paragraph applies here. ### Result Users running on Kubernetes Deployments are pointed to the automatic app-version mechanism instead of bumping it manually. which is now Apache licensed ### Tests Not run - docs only. `sbt "docs/paradox"` builds successfully and the `pekko-management:rolling-updates.html#app-version-from-deployment` extref resolves to a real anchor in Pekko Management. ### References Ports [akka/akka-core@d1e577a8ba](https://github.com/akka/akka-core/commit/d1e577a8ba1bd97d8c775d09632277ef289b17e7) (akka#31942), which is now Apache licensed. -- 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]
