-
Notifications
You must be signed in to change notification settings - Fork 900
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
Move muvaf from maintainers to emeritus #4518
Move muvaf from maintainers to emeritus #4518
Conversation
muvaf
commented
Aug 24, 2023
It has been an honor to serve as maintainer in Crossplane project for the last 4 years. My focus has slightly shifted from infrastructure and I'd like to give room for the next generation of folks stepping up. I have full trust that they will be the best stewards of the project going forward - it's Crossplane, it always reconciles towards the best desired state. "And now, I think I am quite ready to go on another journey. Are you coming?" - Bilbo, the Oldest Hobbit Signed-off-by: Muvaffak Onus <me@muvaf.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Muvaf for all your contributions to the project!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @muvaf! You've been instrumental in helping Crossplane find its footing.
/apis/apiextensions/ @crossplane/crossplane-reviewers @turkenh | ||
/internal/xcrd/ @crossplane/crossplane-reviewers @turkenh | ||
/internal/controller/apiextensions/ @crossplane/crossplane-reviewers @turkenh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure! Fine with me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll merge this as-is and we can update later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so very much @muvaf for all of your efforts to get the project to where it is today, no question in my mind that your contributions were enormous! 💪
edit: lol at the branch name 😂
This commit updates the FunctionComposer to use SSA to create and update composed resources, and to update the XR. I don't believe adopting SSA in this context warrants its own feature flag, since Functions are a new feature in themselves, and we only use SSA to power Functions. It also limits Composition Functions to effecting only an XR's status. The Composition Function pipeline cannot effect an XR's metadata or spec. This is in service of crossplane#4518, which proposes that: * metadata and spec flow claim -> XR -> composed resources * status flow composed resources -> XR -> claim A Function that returns desired XR metadata or spec will be ignored. Signed-off-by: Nic Cope <nicc@rk0n.org>
This commit updates the FunctionComposer to use SSA to create and update composed resources, and to update the XR. I don't believe adopting SSA in this context warrants its own feature flag, since Functions are a new feature in themselves, and we only use SSA to power Functions. It also limits Composition Functions to effecting only an XR's status. The Composition Function pipeline cannot effect an XR's metadata or spec. This is in service of crossplane#4518, which proposes that: * metadata and spec flow claim -> XR -> composed resources * status flow composed resources -> XR -> claim A Function that returns desired XR metadata or spec will be ignored. Signed-off-by: Nic Cope <nicc@rk0n.org>
This commit updates the FunctionComposer to use SSA to create and update composed resources, and to update the XR. I don't believe adopting SSA in this context warrants its own feature flag, since Functions are a new feature in themselves, and we only use SSA to power Functions. It also limits Composition Functions to effecting only an XR's status. The Composition Function pipeline cannot effect an XR's metadata or spec. This is in service of crossplane#4518, which proposes that: * metadata and spec flow claim -> XR -> composed resources * status flow composed resources -> XR -> claim A Function that returns desired XR metadata or spec will be ignored. Signed-off-by: Nic Cope <nicc@rk0n.org>