Job/K8s Installation

From PKC
Revision as of 00:37, 25 July 2021 by Benkoo (talk | contribs)
Jump to navigation Jump to search


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

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

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