hmm at last fixed the nginx controller yaml configs and mtls certificates setttings correct for hmm sio wss connection with websocket method. got alot search engine help since I dont know openssl commands alot and same for nginx-controller topic. gosh it were utter challenging to deploy nginx-controller (with working yaml config) and nginx ingress config and the necessary openssl certificate configs/settings etc etc along with c++ sio client which does not support polling but supports websocket method. it were utter challening to fix this issue. since I dont know about http protocol's websocket and nginx protocol and tls topics alot neither of tls handshake topics but at last fixed. I think i would rest some time before continueing remaining tasks. yep i need some rest time. maybe i might continue tomorrow. this task were uttermost challenging task. I mean configuring the nginx controller to gke and that mtls works with cloud nodejs wss s...
Kayıtlar
yep at last made the nginx controller work for https -> now there is some ws issue but that might be less challenging to fix. turned out certificate configs etc are incorrect in openssl commands. got more correct configs from search engine ai. least the https curl commands now works yep! (mutual tls works in https but wss somehow did not worked) now would try to fix that. possibly http related imho. been working until now without yet fix. but-> error code came from 502 to 400. possbly server has some issue but i think it would be fixed soon. gosh configuring nginx ingress controller and an ingress for a wss that supports mTls on a cloud system is utterly challenging to a person whom is not a devops engineer
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...
yep -> lets see if kubernetes yaml's are correctly deployed. tasks done are like creating docker images and kubernetes yaml generation services deployments (also took help from search engine ai since had not had docker commands in somewhere and ai became utterly useful in revisiting commands or even for yaml templates, i took support from ai since i mean why not :) (normally i did kubernetes yaml file creations last time 1 year ago or so but the ai were very helpful in generating default template without me searching and assembling it. of course needed to change it but for commands (e.g. kubectl commands) ai were utterly useful) hmm installed kubernetes yaml's for both nodejs-app and py oltp app and then now did initial change to library to connect to the GKE static IP/DNS instead of 127.0.0.1:8443 but initial test failed as expected :) possibly configs to be done.
yep time to resume studying yep first task: create docker image docker image created and kubernetes yaml file has been prepared and to check deployment (There is one issue which would be fixed) yep then lets install the py docker image and deploy and modify the required plugin code/library for lua modification and to test. i think these tasks seems as tasks completable today then following day could test and implement code fixes from tests.