|Saturday||11/17/2018 at 01:00PM|
Ask all your questions on Piazza. Assign assignment5 tag to your posts.
To keep your AWS credit usage to minimum, please terminate your k8s stack when you are done working on it.
Setup Continuous Deployment pipeline for your web application. CI/CD pipeline may look something like this:
- Code changes are committed to GitHub. Your build system (TravsiCI or Jenkins) can either monitor GitHub for changes or it can be configured to be notified by GitHub about new commit.
- Clone the repository with latest code and build the container. Container should be tagged with build number. Build number will serve as “version” of your application/container. You may alternatively use date/time for container version number.
- Push the container to your container registry.
- Update your app Deployment using “Rolling Update” strategy with zero (0) downtime.
- Kubernetes Continuous Deploy Plugin for Jenkins
- Jenkins X
- Configuring CI/CD on Kubernetes with Jenkins
- How to build a secure by default Kubernetes cluster with a basic CI/CD pipeline on AWS
- Jenkins X: Easy CI/CD for Kubernetes
- CI/CD and Kubernetes
- OpenShift Pipeline Builds
Releases created after due date will be considered late.
- All work for this assignment must be done on assignment5 feature branch and merged to master when you are dev complete.
- GitHub release must be created from the master branch.
- All team member’s branches must be in-sync. Each team member must create a release in their repository.
- All assignments will be delivered using GitHub releases feature. See GitHub documentation for details on how to create a release.
Following guidelines are for information only and are subject to change at my discretion.
- Demonstrate that your deliverables have met assignment objectives.