วีดีโอ

@@abhilashpatel3036 there is a job which brings this pod up, delete it under the jobs menu. Normally it should go away by itself, but if didn’t try deleting the job. At the very end you may scale down the deployment and back up again

@@foolfactory9732 this is moved to 1.3.0 and it is under development , 1.2.0 is available with some optimizations right now

@@gabrielmartin7404 yup, it is published. It is on v1.2.0. Neo4j.Berries.OGM

@@nowzarifarhad Thanks, I will look into it! Maybe I can use it for some of my Projects.

@@gabrielmartin7404good luck and we appreciate some feedbacks, since it is actively being developed 😊

So kubespray is to boostrap a k8s cluster. You could run it locally, to setup a cluster. The video is also a local environment. I have the machines under virtual box on windows.

@@nowzarifarhad Are you able to connect the kubernetes cluster in the vms to internet which would allow anyone to access the app deployed on the cluster from anywhere? If so and not just as development setup, how did you set it up!

Thanks, the gitlab runner video can be found here Gitlab CI/CD Runners explained in 18 minutes th-cam.com/video/9t9nsAG65-4/w-d-xo.html

I have tested this on azure and open telekom cloud too, but one thing you need to keep in mind. If the pod is using an internal source. For example using a database under “pgsql.pgsql.svc.cluster.local”, when you start debugging, it cannot connect to that address anymore. With database connections it is tricky to test except if you can access the database publicly. For other internal services I mostly change the config to localhost for example and when debugging starts I will port forward those services

@@nowzarifarhad what about this port forwarding. How do we know which port to forward to?

That depends on the configuration you made. Let’s say your service when it is running, has a config which uses “test-service:9000”. Now before you debug just for the purpose of testing, you will change the config to “localhost:9000” now before debugging starts, you will port forward the test-service to your localhost:9000. But be careful that in production, this may kill a part of your app while you are testing, since when the service is accessed via a request, it can not find any services on localhost:9000. To avoid this, you can deploy the same version of the pod again with the localhost config, connected to a prod database which is publicly available with credentials and debug that one. But one thing is that, I think you also could tell the debugger to use a local config and not the one which is online. When I get time, I will try to have more short videos on this

hmm, so on azure, it should assign an IP address automatically to your load balancer ingrersses. Please check if that has happened by azure. That IP address is a virtual one and is connected to a load balancer and that loadbalancer redirects the data to your cluster and azure sets them up automatically. now if all set as above, I would say, first port-forward the gitlab webservice and check if you actually can access that service, maybe the problem is on gitlab installation. If it is ok, then deploy a small nginx pod and test if you can connect to it via your ingress controller. From here I can only recommend these approaches to break down the problem.

hi; i have this problem too,

So the video only covers a self managed kubernetes without a loadbalancer or a floating ip. The cloud providers mostly have a provisioner to provide the ip address to your i gress. For example in Azure; it detects nginx class and assign the ip automatically. On open telekom cloud, you need to buy an elastic ip first, then enter the provisioner info to assign the ip. For GKE I don’t have an experience but it should be documented in the GKE’s ingress documentation. Maybe GKE even offers it’s own ingress controller

Thanks!

Mersi 🫡😊🙏🏼

Yes this is possible but then you need to run the dapr sidecars yourself with the dapr run command. docs.dapr.io/getting-started/install-dapr-cli/ It will run in docker

Hi, thanks Unfortunately I don't have experience with MongoDb. Are you using the MongoDb as the statestore? if so and as I saw dapr needs the Username-Password for it. You need to check the dapr statestore implementation for MongoDb if the implementation needs Username-Password then thats it but you also can fork the branch and change it to your needs? And Kafka, are you using it as a pubsub or with dapr bindings?

@@nowzarifarhad Awesome, I've asked 6 people on all different channels and you're the only one that responded. Thank you very much for your help.