Difference between revisions of "K8s Installation/Context"

Revision as of 01:44, 25 July 2021

Migrating roadmaps.mit.edu to the CI/CD workflow of Personal Knowledge Container PKC.

This job has many smaller tasks:

Abstract Specification
Context	Migrating roadmaps.mit.edu to the CI/CD workflow of Personal Knowledge Container PKC.
Goal	Use Kubernetes as the main deployment and monitoring mechanism for PKC.
Success Criteria	Attain a CI/CD Workflow for software and content deployment

Concrete Implementation
Given Inputs	When Process is executed...	Then, we get Outputs
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.	A detailed manual procedure to install K8s software and PKC data content. Incrementally document installation process in PKC, and slowly migrate manual processes into automated processes by Jenkins, Ansible, and Terraform. These actions should be hyperlinked in corresponding PKC pages.	A fully functional PKC, running content from ROADMAPS.MIT.EDU. Set up a initialization procedure for managing Administrative Accounts for MediaWiki.

Boundary/Safety Conditions of K8s Installation
The above system will be deployed onto AWS and IONOS cloud providers.

@@ Line 8: / Line 8: @@
 #Start using the code base of [[PKC]].
 #Employing [[CI/CD]] practice in building and maintaining the system.
+{{:Job/K8s Installation}}
 [[has LogicModel::K8s Installation]]
 </noinclude>