Difference between revisions of "Job/K8s Installation"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
|criteria=Attain a [[CI/CD Workflow]] for software and content deployment | |criteria=Attain a [[CI/CD Workflow]] for software and content deployment | ||
|outputs=#A fully functional [[PKC]], running content from [https://roadmaps.mit.edu ROADMAPS.MIT.EDU]. | |outputs=#A fully functional [[PKC]], running content from [https://roadmaps.mit.edu ROADMAPS.MIT.EDU]. | ||
|process=Currently working with a manually driven command line actions, and over time, a set of automated and human triggered actions to deploy both software and content. | |process=#Currently working with a manually driven command line actions, and over time, a set of automated and human triggered actions to deploy both software and content. | ||
#All actions will be manually documented in [[PKC]], and will be integrated with [[Jenkins]], [[Ansible]], and [[Terraform]]. | |||
|inputs=#[[PKC]] code base | |inputs=#[[PKC]] code base | ||
# The original data content from [https://roadmaps.mit.edu ROADMAPS.MIT.EDU] | # The original data content from [https://roadmaps.mit.edu ROADMAPS.MIT.EDU] | ||
Revision as of 07:28, 24 July 2021
TO BE DEPRECATED: When you see this, please consider moving the logic model below from Template:Logic Model to Template:LogicModel
| 1. Context |
In preparation to deploy the Kubernetes version of PKC deployment. | ||
| 2. Goal |
Use Kubernetes as the main deployment and monitoring mechanism for PKC. | ||
| 3. Success Criteria |
Attain a CI/CD Workflow for software and content deployment | ||
| 4. Outputs | 5. Process | 6. Inputs | |
|
| ||
| 7. Boundary Conditions |
The above system will be deployed onto AWS and IONOS cloud providers | ||