Difference between revisions of "Job/K8s Installation"
Jump to navigation
Jump to search
Line 3: | Line 3: | ||
|goal=Use [[Kubernetes]] as the main deployment and monitoring mechanism for [[PKC]]. | |goal=Use [[Kubernetes]] as the main deployment and monitoring mechanism for [[PKC]]. | ||
|criteria=Attain a [[CI/CD Workflow]] for software and content deployment | |criteria=Attain a [[CI/CD Workflow]] for software and content deployment | ||
|outputs= | |outputs={{:Output/K8s_Installation}} | ||
#All actions will be manually documented in [[PKC]], and all processes and activities driven by [[Jenkins]], [[Ansible]], and [[Terraform]], will be hyperlinked in specific [[PKC]] pages. | #All actions will be manually documented in [[PKC]], and all processes and activities driven by [[Jenkins]], [[Ansible]], and [[Terraform]], will be hyperlinked in specific [[PKC]] pages. | ||
|inputs=#[[PKC]] code base | |inputs=#[[PKC]] code base |
Revision as of 00:40, 25 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 |
Migrating version 1.17 of Kubernetes and Version 1.33 of MediaWiki to version 1.21 Kubernetes and Version 1.35 PKC. | ||
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 | |
|
{{{process}}} |
| |
7. Boundary Conditions |
The above system will be deployed onto AWS and IONOS cloud providers |