Hi Vincent We are currently running Jenkins (EC2) and Kubernetes (EC2) and are trying to migrate from Kubernetes to EKS for ease of management. I was hoping to do one step at a time and reuse as much as possible in Jenkins. But if moving Jenkins into EKS would make life a lot easier then i can definitely do that.
With the first approach, i will have to run the deployments by running the kubectl apply commands right? -------- Regards, Junaid On Fri, Sep 6, 2019 at 10:32 AM Vincent Latombe <[email protected]> wrote: > You can provide a kubeconfig file as credentials. You'll > need aws-iam-authenticator set up on the EC2 instance you have Jenkins > installed on, as well as running your EC2 instance with an instance profile > with the ability to log in to your EKS cluster. > > Out of curiosity, why don't you run your Jenkins instance directly in your > EKS cluster? Then it would use directly service account credentials. > > Vincent > > > Le jeu. 5 sept. 2019 à 00:06, Junaid Mukhtar <[email protected]> a > écrit : > >> >> Hi Team >>> >>> We are using Jenkins to run build, test and deploy jobs to our KOPS >>> Cluster successfully without any issues. Jenkins is running on a dedicated >>> EC2 instance >>> >>> We are now planning to switch over to EKS Cluster and want to point >>> Jenkins to the new EKS cluster to perform the same actions. >>> >>> We are using Kubernetes Plugin for the KOPS cluster which uses >>> certificate and username/password for authentication. But for EKS AWS uses >>> aws-iam-authenticator that goes into the kubeconfig to generate on the fly >>> tokens and so far we haven't been able to come up with a way to use >>> aws-iam-authenticator to integrate Jenkins with EKS cluster. >>> >>> I would be really greateful if you could point me in a right direction >>> or share with me the steps to integrate Jenkins with EKS cluster. >>> >>> -------- >>> Regards, >>> Junaid >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/CAPO_fvoE9RnNETYENS%3DfRdmsgbh-hktj7fQm3Q_mp_7S0UG%2BFw%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-users/CAPO_fvoE9RnNETYENS%3DfRdmsgbh-hktj7fQm3Q_mp_7S0UG%2BFw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CAH-zGCjQARuJkvoUkUJ33_gfj2A1tAgg%2B7%2BN4XfCuG_-CPBByA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAH-zGCjQARuJkvoUkUJ33_gfj2A1tAgg%2B7%2BN4XfCuG_-CPBByA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPO_fvrWSa9KYniO8VybwoA6gW2GDRDsQF49bAHVNiZ4Y7gECQ%40mail.gmail.com.
