Hi all, For https://github.com/apache/pulsar/pull/13376, I have done some tests to verify the upgrade of Pulsar Functions from root image to non-root image. The test runs on my local machine with KinD cluster, with a fresh Pulsar +auth 2.8.2 cluster. The cluster uses Kubernetes Runtime and multiple functions been created and runs fine. Then the upgrade uses `helm upgrade` with the self built docker image (freeznet/pulsar-all:2.10.0-SNAPSHOT) based on https://github.com/apache/pulsar/pull/13376, after the broker and functions worker been upgraded, I have used `pulsar-admin functions restart` to trigger the function upgradation, and the existing function upgraded to non-root image and works fine after restart. I have also tested sinks and sources as well.
So from my tests, the non-root image works fine and #13376 should not block the 2.10 release. On 2022/02/09 08:25:00 PengHui Li wrote: > Hi all, > > Sorry for the late reply, due to my vacation these days, we got a delay > here. > > Most of the changes of 2.10.0 are getting merged, for now, there are 14 > opened PRs(10 approved) > https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+milestone%3A2.10.0 > > I will take care of them and try to get them merged. > After the above PRs get merged, I will build the release and start the vote. > Please let me know if you have any questions about the 2.10.0 release. > And, also looking forward to more people taking a look at the opened PRs. > > Regards, > Penghui > > > > > On Tue, Jan 4, 2022 at 7:56 AM Sijie Guo <guosi...@gmail.com> wrote: > > > +1. > > > > All make sense to me! > > > > We probably need to move to the feature frozen stage in order to cut a > > release at the end of January. > > > > - Sijie > > > > On Sun, Dec 26, 2021 at 8:46 PM PengHui Li <peng...@apache.org> wrote: > > > > > Hi, everyone > > > > > > I hope you’ve all been doing well. I would like to start an email thread > > to > > > discuss features that we planned for 2.10.0. > > > According to the time-based release plan > > > https://github.com/apache/pulsar/wiki/PIP-47%3A-Time-Based-Release-Plan, > > > we should release 2.10.0 at the end of December 2021, since we have > > reached > > > the end of December, > > > I would like to target the 2.10.0 to the end of January 2022 > > > > > > There are some powerful features and enhancements in 2.10.0 such as > > > > > > - PIP 84: Message redelivery epoch > > > - PIP 104: Add new consumer type: TableView > > > - PIP 106: Negative acknowledgment backoff > > > - PIP 110: Topic customized metadata support > > > - PIP 117: Change Pulsar standalone defaults > > > - PIP 118: Do not restart brokers when ZooKeeper session expires > > > - PIP 119: Enable consistent hashing by default on KeyShared dispatcher > > > - PIP 120: Enable client memory limit by default > > > - PIP 121: Pulsar cluster level auto failover > > > - PIP 123: Pulsar metadata CLI tool > > > - Metadata service batch operations > > > - RocksDB metadata service backend > > > - Etcd metadata service backend > > > - Ack timeout redelivery backoff policy > > > - Global topic policies > > > > > > Most of them have been completed, some work in progress we need to try to > > > complete within 2 weeks. > > > This can give me a 2 week buffer period to prepare for release and > > complete > > > the release vote. > > > For the unfinished parts, we can move them to 2.11.0. > > > > > > Some proposals are just being discussed, so I do not list them because > > I'm > > > not sure if we can complete them in two weeks. > > > > > > You can find all the change lists from > > > > > > > > https://github.com/apache/pulsar/pulls?q=milestone%3A2.10.0+-label%3Arelease%2F2.9.1 > > > There are more than 500 commits. > > > > > > If I missed something or you have any suggestions please let me know. > > > > > > Regards, > > > Penghui > > > > > >
