Difference between revisions of "Job/K8s Installation"

From PKC
Jump to navigation Jump to search
Line 1: Line 1:
{{Template:Logic Model
{{Template:Logic Model
|context=Migrating version 1.17 of [[Kubernetes]] and Version 1.33 of [[MediaWiki]] to version 1.21 [[Kubernetes]] and Version 1.35 [[PKC]].
|context={{:Context/K8s Installation}}
|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

Revision as of 01:30, 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 roadmaps.mit.edu to Kubernetes-based Personal Knowledge Container PKC. Added more elaboration.

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
  1. A fully functional PKC, running content from ROADMAPS.MIT.EDU.
  2. Set up a initialization procedure for managing Administrative Accounts for MediaWiki.
  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. 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.
7. Boundary Conditions

The above system will be deployed onto AWS and IONOS cloud providers


K8s Installation