Hi Andreas, Since I am not using these components, I didn't test them in my lab. However, as I mentioned in the wiki thread, ( https://wiki.onap.org/display/DW/Create+AAF+CA+certificates?focusedCommentId=188514380&refresh=1693858440010#comment-188514380 ) the components, such as dcaegen2, have their own cert init container with the aaf certificate embedded in the container image. I think this might be the reason why SO, SDC, and CDS broke if they have their own cert init containers.
I also found that onap-aaf-sms-preload and onap-dmaap-bc-dmaap-provisioning jobs also broke in my environment. So, I can not provide any idea now. Regards, Louis. On Tue, Sep 19, 2023 at 10:14 PM, Andreas Geissler wrote: > > > with my patch so far the AAF component is up and running. > But the clients using the cert-initializer (e.g. SO, SDC, CDS) still fail. > > The aaf-config container logs show valid certificates: -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#24554): https://lists.onap.org/g/onap-discuss/message/24554 Mute This Topic: https://lists.onap.org/mt/100888379/21656 Mute #aaf:https://lists.onap.org/g/onap-discuss/mutehashtag/aaf Mute #sdc:https://lists.onap.org/g/onap-discuss/mutehashtag/sdc Mute #x509:https://lists.onap.org/g/onap-discuss/mutehashtag/x509 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
