Hey Master Pro Devops guy, thanks a lot for this explanation. First time I actually had to reduce video speed when seeing an IT video. Your information is concrete, detailed, and most importantly, to the point. Have a wonderful day!
ปีที่แล้ว +1
And how do we proceed now, without Docker running on EC2?
You can use a sidecar on the jenkins agent pod, and run the docker:dind image to build as an alternative. This works quite well since it decouples you from the nodes container runtime
Thank you for the wonderful video. Just one thing, the background music starting at 6:00 is distracting/noisy. Would be helpful to just hear the explanation in a clear voice instead :)
Currently fighting with Jenkins we deployed via Helm, to run agent pods with kubectl and nodejs on it, the jenkins-slave image dont have curl neither wget so there is no way to just download it and install on statlrt
I'm having a problem while build the docker images, internet connectivity is available when i gave yum "RUN yum update" in the dockerfile...The slave node has the internet connectivity but in Dockerfile it shows Network Not Reachable....Can you please help me on this...
Really good and informative. To the point and sweet. I loved it. I; however, think that one must leverage HELM for deployments. The benefits are too great when it comes to release management to ignore so that's something I will continue to get done and working. On the other hand, my EKS Cluster uses both Windows and Linux worker nodes so I'll have to figure out how to get the two different worker nodes pods with the respective OS Images created for the desired worker os.
Awesome tutorial. I tried and everything worked fine . Only one problem , after creating new pipeline job with agent set to any , i can see many pods are getting created and end up in error. The error on jenkins says something like "jenkins label not found". Any idea on this ?
But since I set the user to 1001 and group to 1950, Im not able to perform andy "sudo" commands or SCP commands in my pipeline ( scp returns unknown user: 1001). Sorry Im pretty new to Devops, but how can we tackle this in Jenkins ?
I'm blocked at 10:33 :( I can't seem to make the port forwarding work for some reason, I keep getting Connection Refused errors when accessing 127.0.0.1:8080, and also the command hangs and doesn't do anything. Any tips on that?
Hello, I have an existing environment which is sitting in AWS EC2 and now I’m in the process migrating designing the solution to migrate into AWS EKS. Here is our existing legacy environment: [Jenkins Master with 1 Windows and 1 Linux agent ] - Installed on Aws ec2. Modernization Requirement: Jenkins will be deployed into AWS EKS with same Jenkins architecture. What’s the best way to deploy Windows and Linux agent pods in Aws eks cluster ? Can some one help me here ?
Just amazing. If I run more than one Jenkins jobs in the same time, will EKS provision more slaves for that? Also how to deploy Blue/Green through that declarative Jenkinsfile ?
I followed your steps and success to deploy under the same namespace of Jenkins. Now, I need to deploy under a different namespace, so I created a namespace and then edit configmap by adding the namespace. but error message got out that cannot get resource "configmaps" in API group "" in the namespace "xxx". I tried also to do with script command "./kubectl apply -n xxx -f ./kubernetes/configmaps/configmap.yaml", but got the same output error. any advice?
That sounds like you missed something from a glance... perhaps either the jenkins agent is not running as the correct service account and does not have permission to "get" configmap from namespace "xxx" or you've missed the RBAC permissions on the service account.
You might need to get a terminal into the agent while its running, and test out docker commands from there to ensure its working and to ensure the docker commands are running on the correct agent
@@MarcelDempers It generated two containers in my pod for some reason, which was causing the confusion. Started again and all looking good now. Keep up the good work :)
Good job man, I’m planning to use kaniko image builder so that I won’t need docker daemon. I would like to have Jenkins UI behind an ingress/API-gateway so that my developers won’t have to do port forwarding. I will update how it goes. What I would like to see is to make EKS control plane’s API server private, so that it can only be accessible from “my-network”.
Not sure if I understood everything but you can configure EKS to be a internal endpoint and only answer from a single VPC where you can route as you'd like. For the Jenkins what I had used in the past is having a internal load balance for the Jenkins instance and had a internal domain on route53 that was available on site thru a STS vpn. About kaniko take a look at Makisu from Uber. I didn't try any of them but Makisu seems more "docker CLI" like and has some cool inside commands for layering control.
Gustavo Bosmak thanks, I’ll try it out. With regards to EKS control plane’s Endpoint, this is what I meant docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html
![[ Kube 25 Discussion 1 ] Configuring Jenkins to connect to Kubernetes cluster](/img/n.gif)
Man, this is pure gold. Thank you so much for your work!
Hey Master Pro Devops guy, thanks a lot for this explanation. First time I actually had to reduce video speed when seeing an IT video. Your information is concrete, detailed, and most importantly, to the point. Have a wonderful day!
And how do we proceed now, without Docker running on EC2?
Appreciate your efforts! Great video 👍
This is awesome! However, I am running k8s v1.24 where docker support is removed. How does this impact the docker builds?
You can use a sidecar on the jenkins agent pod, and run the docker:dind image to build as an alternative.
This works quite well since it decouples you from the nodes container runtime
Great work! Working on moving Jenkins infra over to EKS so this was really helpful in seeing what setup for that entails :)
Another great video with all the details! Thanks for putting your videos up!
Excellent explanation..!!! Straight to the point..looking for more videos like this..!!!
i am unable to build jenkins agent with jdk 17 and higher version of docker. do you have latest image for the same?
Lot of missing, where did you get the kubernetes url? second how did you configure the jenkins credential? where did you get those values??
I agree with the comment below. This is pure gold :)
Thank you for the wonderful video. Just one thing, the background music starting at 6:00 is distracting/noisy. Would be helpful to just hear the explanation in a clear voice instead :)
Currently fighting with Jenkins we deployed via Helm, to run agent pods with kubectl and nodejs on it, the jenkins-slave image dont have curl neither wget so there is no way to just download it and install on statlrt
I'm having a problem while build the docker images, internet connectivity is available when i gave yum "RUN yum update" in the dockerfile...The slave node has the internet connectivity but in Dockerfile it shows Network Not Reachable....Can you please help me on this...
Really good and informative. To the point and sweet. I loved it. I; however, think that one must leverage HELM for deployments. The benefits are too great when it comes to release management to ignore so that's something I will continue to get done and working. On the other hand, my EKS Cluster uses both Windows and Linux worker nodes so I'll have to figure out how to get the two different worker nodes pods with the respective OS Images created for the desired worker os.
Awesome tutorial. I tried and everything worked fine . Only one problem , after creating new pipeline job with agent set to any , i can see many pods are getting created and end up in error. The error on jenkins says something like "jenkins label not found". Any idea on this ?
Really love your content mate! Keep it up! Cheers
But since I set the user to 1001 and group to 1950, Im not able to perform andy "sudo" commands or SCP commands in my pipeline ( scp returns unknown user: 1001). Sorry Im pretty new to Devops, but how can we tackle this in Jenkins ?
how can I get user Id for docker ? I followed another vedio and didt configure ssh when launch an eks cluster, any workaround ?
Great channel! Keep up the helpful content! Subbed
I'm blocked at 10:33 :( I can't seem to make the port forwarding work for some reason, I keep getting Connection Refused errors when accessing 127.0.0.1:8080, and also the command hangs and doesn't do anything. Any tips on that?
same here, I am using Cloud9 as my IDE
I finally decided to use LoadBalancer instead of ClusterIP for the learning purpose
stuck here,, anybody has an idea? even i enable eks cluster endpoint access to public but still not able to see jenkins page?
Hello,
I have an existing environment which is sitting in AWS EC2 and now I’m in the process migrating designing the solution to migrate into AWS EKS.
Here is our existing legacy environment:
[Jenkins Master with 1 Windows and 1 Linux agent ] - Installed on Aws ec2.
Modernization Requirement:
Jenkins will be deployed into AWS EKS with same Jenkins architecture.
What’s the best way to deploy Windows and Linux agent pods in Aws eks cluster ?
Can some one help me here ?
Awesome man. Thank you for your time.
Just amazing. If I run more than one Jenkins jobs in the same time, will EKS provision more slaves for that? Also how to deploy Blue/Green through that declarative Jenkinsfile ?
I followed your steps and success to deploy under the same namespace of Jenkins. Now, I need to deploy under a different namespace, so I created a namespace and then edit configmap by adding the namespace. but error message got out that cannot get resource "configmaps" in API group "" in the namespace "xxx". I tried also to do with script command "./kubectl apply -n xxx -f ./kubernetes/configmaps/configmap.yaml", but got the same output error. any advice?
That sounds like you missed something from a glance... perhaps either the jenkins agent is not running as the correct service account and does not have permission to "get" configmap from namespace "xxx" or you've missed the RBAC permissions on the service account.
Great video! Im getting "script.sh: docker: not found" in my agent, even though the docker executable is definitely there and accessible. Any ideas?
You might need to get a terminal into the agent while its running, and test out docker commands from there to ensure its working and to ensure the docker commands are running on the correct agent
@@MarcelDempers It generated two containers in my pod for some reason, which was causing the confusion. Started again and all looking good now. Keep up the good work :)
Good job man, I’m planning to use kaniko image builder so that I won’t need docker daemon. I would like to have Jenkins UI behind an ingress/API-gateway so that my developers won’t have to do port forwarding. I will update how it goes.
What I would like to see is to make EKS control plane’s API server private, so that it can only be accessible from “my-network”.
Not sure if I understood everything but you can configure EKS to be a internal endpoint and only answer from a single VPC where you can route as you'd like. For the Jenkins what I had used in the past is having a internal load balance for the Jenkins instance and had a internal domain on route53 that was available on site thru a STS vpn.
About kaniko take a look at Makisu from Uber. I didn't try any of them but Makisu seems more "docker CLI" like and has some cool inside commands for layering control.
Gustavo Bosmak thanks, I’ll try it out. With regards to EKS control plane’s Endpoint, this is what I meant docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html
Awesome. Thank you so much.
Awesome
Great nice one.