yep turns out wss with mutualTLS installment with ingress of gce or nginx version is kind of challenging alot.
--> the issue in gce ingress is -> hmm the v1.0 config versiosn do not enable health check api's to accept certificate.
-> the issue in nginx -> i think its because of its rejection of certificate without san fields.
so yep whilst I know nothing of nginx stuff, had to learn some info in these days with also help of search engine ai of course, and so but still hadnt been able to fix issue.
but i think maybe nginx version which works with either wss termination at nginx ingress itself or else nginx ingress default might fix after checking this certificate issue.
gosh, it were utter challenging to try to setup proxy pass in ingress whilst not being a devops engineer.
and one thing is that via search engine ai, I learnt that i dont have to use lua based code add feature of nginx but rather stateful service concept of kubernetes provides such thingy. that i hadnt known what its for if search engine hadnt mentioned. (yep not a devops engineer, there by of course i dont know what is stateful sets concept of kubernetes until now)
so instead of ip then hostname field is used in kubernetes service which alleviates any NAT issue or such issues. but this is not the issue currently that i currently try to fix the nginx ingress itself since it has issue first to fix. the routing is secondary task, in any case there is also lua method avail also. (which i checked out how to add lua script )
Yorumlar
Yorum Gönder