-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@tomkerkhove stepping down as maintainer #115
Comments
It’s hard to believe you’re stepping down as a maintainer – KEDA wouldn’t be where it is today without your hard work and dedication. You’ve been such a key part of this project from the start, and it’s been an absolute pleasure working alongside you. While it’s definitely sad to see you go, I completely understand your decision. KEDA’s success and growth speak volumes about the impact you’ve had, and I’m excited to see where the project goes next, even though it won’t be the same without you. Wishing you all the best in whatever comes next – you’ve earned it! And of course, we’ll always be happy to see you around if you decide to drop by (and also finally would like to start coding in Golang 🔥 😄 ). Thanks again for everything! |
Thanks for the kind words! I'm confident that KEDA is in the right hands though!
I deserve this :D |
Sorry, I couldn't resist :-P 😄 I hope you don't mind :) |
By all means, fire away! |
I read this sad, as you are part of KEDA. I fully agree with @zroubalik words, KEDA wouldn't have been here without your awesome job and your commitment, working with you have been a huge pleasure and your vision and ideas will be something that we will miss (at least me). Said this, I totally understand your decision and I wish the best for you in the future. You will be always part of KEDA and this community will be happy whenever you want to appear here again (at least to say, hello!) I can't say anymore than thanks for all the time, effort and love that you have shared with KEDA, without you, KEDA probably wouldn't ever have reached the graduated status. |
Relates to #115 Signed-off-by: Tom Kerkhove <[email protected]>
Thank you @JorTurFer! The pleasure was all mine. |
Years ago, I started Promitor as an open-source project because fundamental autoscaling capabilities in Kubernetes were lacking (other than for CPU/memory).
The day I saw a preview of KEDA (then called Koree) by @jeffhollan I was instantly solved - KEDA solved this problem and started to get involved back in 2019. Fast forward to today where KEDA is a CNCF Graduated project that is the defacto app autoscaling solution for Kubernetes.
It's has been an honour to be part of the KEDA and serve as a maintainer to help with CNCF donation to Sandbox, Incubation and even Graduation - Something I've never expected.
The adoption of KEDA has really blown my mind and it still baffles me that companies like Xbox, FedEx, Microsoft, Reddit, Grafana and many others are building their platforms on top of us. Some of the ones I'm most proud of are ones I cannot share (🙃) are the ones I come across in my personal life (tip: 🕹️).
Last but not least, I've had to honor to meet and get to know people better such as @anirudhgarg, @zroubalik , @JorTurFer, @caniszczyk, @yaron2 and many others.
However, today I am stepping down as a maintainer. After more than 5 years it is time for me to make place for new community members to take over and share fresh ideas.
Additionally, over the past months/year I've been struggling to put enough time in being a maintainer that it no longer feels right to me so this feels like the best course of action for KEDA & myself.
I will always, genuinely, 💘 KEDA and autoscaling will always be my passion.
I'm curious to see how KEDA will continue to evolve and always keep in mind - Make autoscaling dead simple, and focus on the end-user experience!
PS: If maintainers want me to stick around behind the scenes to help onboard Jan who is 99% sure becoming a maintainer then I'm happy to do so. My endorsement for him is completely unrelated to me stepping down, he just freakin' deserves it.
The text was updated successfully, but these errors were encountered: