Thank you Pavel. The insights about interaction between AAI and AAF was helpful. I disabled AAF as you recommended and we are now *able* to communicate with AAI :-) !!
We have already tried with the default values and they work. However in our dev environment, each dev is allocated a separate namespace, persistent mountpath and nodeport-prefix and we need to stick to them. What we really want is working ONAP with AAF enabled. AAF is actually up and running in my dev environment but AAI isn't able to communicate with it. Do you know if we can generate AAF cert using a specific namespace (rather than onap) and put it under the oom/kubernetes/aai/charts/aai-traversal/resources/config/aaf/org.onap.aai.keyfile. I suppose that's the cert you are talking about? That would be really help unblock us. Regards, Rahul -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13827): https://lists.onap.org/g/onap-discuss/message/13827 Mute This Topic: https://lists.onap.org/mt/28195431/21656 Mute #aai: https://lists.onap.org/mk?hashtag=aai&subid=2740164 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
