A docker hub account to be used as our "master" repo master repo.You can also use an IAM Role if you prefer ( give the above permissions and get the credentials ).you need the Account IAM User "Access Key ID" & "Secret access key" because you will needed later to configure AWS CLI !!!!!.
Deployments - replicates our application across our kubernetes nodes and allows us to do a controlled rolling update of our software across the fleet of application instances.In order to deploy the application with Kubernetes you will use the following resources: Jenkins Sonarqube - it lets you centralize the configuration of SonarQube server connection details in Jenkins global configuration.Jenkins NodeJS - Provides Jenkins integration for NodeJS & npm package.You can provide region and profile information or let Jenkins assume a role in another or the same AWS account. Jenkins Pipeline AWS Steps - allows users use the withAWS step to get AWS authorization for the nested steps.
Jenkins Blue Ocean Plugin - allows users to graphically create, visualize and diagnose Continuous Delivery (CD) Pipelines.Jenkins Pipelines - define our build pipeline declaratively and keep it checked into source code management alongside our application code.In order to accomplish this goal you will use the following Jenkins plugins: If you are not familiar with basic Kubernetes concepts, have a look at , Jenkins and Sonarqube to orchestrate the software delivery pipeline and its deployment in AWS EKS using a "ROLLING UPDATE STRATEGY". This guide will take you through the steps necessary to BUILD a CI/CD pipeline UDACITY DEVOPS CAPSTONE PROJECT: Build a Continuous Integration / Continuous Deployment Pipeline (CI/CD) with Jenkins and Kubernetes