Passing configuration as POJOs (v6) #3181

Activity

1. csviri

   added this to the 6.0 milestone on Feb 24, 2026
2. Lavanya-N24 commented on Aug 17, 2026

   

   Lavanya-N24

   on Aug 17, 2026

   Contributor

   More actions

   Hi @csviri, I would like to work on this issue for the v6 milestone.

   Before opening a PR, could you provide any pointers on:

   1. The target package/classes for the new POJO configuration and Builders?
   2. Any specific considerations to keep in mind regarding how Spring Boot and Quarkus extensions consume this configuration?

   Thanks!
3. csviri commented on Aug 17, 2026

   

   csviri

   on Aug 17, 2026

   Last edited by csviri

   CollaboratorAuthor

   More actions

   Hi @Lavanya-N24 , thank you for reaching out

   we plan to work on v6 just sometimes next year, we are only in a phase to gather issues, which might or might not end up in v6. This issue is an example of such. So I'm not against working on this, and see where it leads, but note that

   1. might not be merged at the end
   2. would be released no sooner as Q2 2027

   If you are interested I can try to find an issue for you.
4. Lavanya-N24 commented on Aug 17, 2026

   

   Lavanya-N24

   on Aug 17, 2026 via email

   Contributor

   More actions

   Thank you for explaining! I understand that v6 is still in the planning phase and that this issue may or may not be included in the final release. I would definitely prefer to work on an issue that is more likely to be merged in the near term, so if you could suggest an issue that would be a good fit for me, I’d really appreciate it. I’d be happy to explore it and work on it. Thank you for offering to help me find one!

   …

   On Mon, Aug 17, 2026, 7:25 PM Attila Mészáros ***@***.***> wrote: *csviri* left a comment (operator-framework/java-operator-sdk#3181) <#3181 (comment)> Hi @Lavanya-N24 <https://github.com/Lavanya-N24> , thank you for reaching out we plan to work on v6 just sometimes next year, we are only in a phase to gather issues, which might or might not end up in v6. This issue is an example of such. So I'm not against working on this, and see where it leads, but note that 1. might not be merged at the end 2. would be released no sooner as Q2 2027 If you are interested I can try to find an issue for you. — Reply to this email directly, view it on GitHub <#3181?email_source=notifications&email_token=BNLOGEZWACBMKZNI7LSPI2D5KMFDNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZRGY4DQMBUHE32M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5316880497>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BNLOGE4FCN5JTVYKANGCVYT5KMFDNAVCNFSNUABFKJSXA33TNF2G64TZHMYTQOBVHEZDSMZTHNEXG43VMU5TGOJYGUZDONBVHE2KC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BNLOGE22HRLTOT6AD7SAQIL5KMFDNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZRGY4DQMBUHE32M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/BNLOGE4OSTJWKOCVLJWLLGD5KMFDNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZRGY4DQMBUHE32M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>
5. csviri commented on Aug 18, 2026

   

   csviri

   on Aug 18, 2026

   CollaboratorAuthor

   More actions

   Hi @Lavanya-N24, pls take a look on these, and feel free to choose any subset :)

   #2304
   #1514
   #1304
   #2267

   Ordered by complexity. Let's continue discussion under the target issue, so we don't spam under this issue :)
   (might also delete these last 2 comments if no objections)

   thx!
6. Lavanya-N24 commented on Aug 18, 2026

   

   Lavanya-N24

   on Aug 18, 2026

   Contributor

   More actions

   okay