Amazing video! I love it! Please, do more videos like that. Is this a vanilla k8s cluster? I didn't understand if you used an external Postgres db instead of the Gitlab built-in one. Anyway, congratulations! 👏
Thank you. About the question, yes I used an external postgres, but it was installed on the same k8s but you can also have it outside. So if you notice in the config which I have shared, the postgres.install is false. This gitlab was installed on a vanilla k8s cluster.
I encountered a roadblock following the video on GKE, at the @12:58 mark. My progress halted because I couldn't allocate an external IP, and I found myself in a situation where I had to wait for the ingress controller to provide an external IP address before I could proceed to add it to the DNS. It seemed like a standstill in the process.
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
You gave a show. Congratulations. Now a question: in your opinion, Farhad, what are the advantages of having gitilab on premise, considering that the same application is in the cloud, and with the same or even more functionalities. Thank you.
Thank you. Well installing it on premise is only necessary for companies which need to follow specific data policy regulations. If a company can ignore specific privacy policy needs and data security standards, it is recommended to use the managed gitlab on the cloud, since they don't need to manage it on their own.
so in the video I used the cert-manager from the gitlab chart. the gitlab configures an issuer from cert-manager to issue a certificate from let's encrypt.
I tried to deply GitLab in Azure k8s with terraform and helm,but when I try to connect to the ingress controller external ip address I get 403 error. I suspect it has something to do with the thing you mentioned in your video
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.
![Chlöe - Shake (Feat. Jeremih) [Official Visualizer]](http://i.ytimg.com/vi/aDs_1ufpfv8/mqdefault.jpg)
Cool man I've got a lot to learn
Top notch video . Please , make more on this topic. Thank you.
Thanks, working on a new one :)
Extremely beneficial! Appreciate you sharing this valuable information.
If you have or will have a part 2 video, please share the link somewhere here.
Thanks for your comment :) gitlab runners can be found here ruclips.net/video/9t9nsAG65-4/видео.html @@aqsoft295
Amazing video! I love it! Please, do more videos like that. Is this a vanilla k8s cluster? I didn't understand if you used an external Postgres db instead of the Gitlab built-in one.
Anyway, congratulations! 👏
Thank you.
About the question, yes I used an external postgres, but it was installed on the same k8s but you can also have it outside. So if you notice in the config which I have shared, the postgres.install is false.
This gitlab was installed on a vanilla k8s cluster.
You forgot the Gitlab runner part or I am missing something? But thanks for the amazing video.
Thanks, the gitlab runner video can be found here
Gitlab CI/CD Runners explained in 18 minutes
ruclips.net/video/9t9nsAG65-4/видео.html
I encountered a roadblock following the video on GKE, at the @12:58 mark. My progress halted because I couldn't allocate an external IP, and I found myself in a situation where I had to wait for the ingress controller to provide an external IP address before I could proceed to add it to the DNS. It seemed like a standstill in the process.
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
You gave a show. Congratulations. Now a question: in your opinion, Farhad, what are the advantages of having gitilab on premise, considering that the same application is in the cloud, and with the same or even more functionalities. Thank you.
Thank you. Well installing it on premise is only necessary for companies which need to follow specific data policy regulations. If a company can ignore specific privacy policy needs and data security standards, it is recommended to use the managed gitlab on the cloud, since they don't need to manage it on their own.
Thank you @nowzarifarhad Your answer helped a lot.I wish you even more success.👏👏
Thank u for this amazing video. how did you handle https certificat ?
so in the video I used the cert-manager from the gitlab chart. the gitlab configures an issuer from cert-manager to issue a certificate from let's encrypt.
@@nowzarifarhad thank u 🙏
I tried to deply GitLab in Azure k8s with terraform and helm,but when I try to connect to the ingress controller external ip address I get 403 error. I suspect it has something to do with the thing you mentioned in your video
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,
where is the pv.yaml