Job/K8s Installation

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
A fully functional PKC, running content from ROADMAPS.MIT.EDU. Set up a initialization procedure for Admin password for MediaWiki for this new release.	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 all processes and activities driven by Jenkins, Ansible, and Terraform, will be hyperlinked in specific PKC pages.	PKC code base The original data content from ROADMAPS.MIT.EDU Knowledge of Kubernetes and the CleanSlate project PKC code base All installation must start with rigorous access to Administrative Accounts. The original data content from ROADMAPS.MIT.EDU Knowledge of Kubernetes and the CleanSlate project Minimally 3 Virtual Machine instances Ansible already setup for the administrative machine Install Kubernetes software on all three following this procedure Kubernetes Installation Ingress Configuration, combined with some SSH license setup for HTTPS. Security Groups are configured to enable necessary ports.
7. Boundary Conditions	The above system will be deployed onto AWS and IONOS cloud providers