Difference between revisions of "Job/K8s Installation"

From PKC
Jump to navigation Jump to search
 
(25 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Template:Logic Model
{{Template:Logic Model 2
|context=In preparation to deploy the [[Kubernetes]] version of [[PKC]] deployment.
|name=K8s Installation
|goal=Use [[Kubernetes]] as the main deployment and monitoring mechanism for [[PKC]].
|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].
|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.
|inputs=#[[PKC]] code base 
# The original data content from [https://roadmaps.mit.edu ROADMAPS.MIT.EDU]
# Knowledge of [[Kubernetes]] and the [http://github.com/xlp0/CleanSlate CleanSlate] project
|boundaries= The above system will be deployed onto [http://aws.com AWS] and [http://ionos.com IONOS] cloud providers
}}
}}
<noinclude>
=Related Pages=
* [[has LogicModel::K8s Installation]]
</noinclude>

Latest revision as of 04:03, 30 July 2021

Logic Model (K8s Installation) Template:LogicModel 07 30, 2021
Abstract Specification
Context Migrating roadmaps.mit.edu to Kubernetes-based Personal Knowledge Container PKC. Added more elaboration.


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
  1. PKC code base
  2. All installation must start with rigorous access to Administrative Accounts.
  3. The original data content from ROADMAPS.MIT.EDU
  4. Knowledge of Kubernetes and the CleanSlate project
  5. Minimally 3 Virtual Machine instances
  6. Ansible already setup for the administrative machine
  7. Install Kubernetes software on all three following this procedure Kubernetes Installation
  8. Ingress Configuration, combined with some SSH license setup for HTTPS.
  9. Security Groups are configured to enable necessary ports.
  1. A detailed manual procedure to install K8s software and PKC data content.
  2. 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.
  1. A fully functional PKC, running content from ROADMAPS.MIT.EDU.
  2. 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.


Related Pages

Retrieved from "https://pkc.pub/index.php?title=Job/K8s_Installation&oldid=7830"