Difference between revisions of "Job/K8s Installation"

From PKC
Jump to navigation Jump to search
Line 4: Line 4:
|criteria=Attain a [[CI/CD Workflow]] for software and content deployment
|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].
|outputs=#A fully functional [[PKC]], running content from [https://roadmaps.mit.edu ROADMAPS.MIT.EDU].
#Set up an initial [[Admin password for MediaWiki]] for this new release.
#Set up a initialization procedure for [[Admin password for MediaWiki]] for this new release.
|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.
|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.
#All actions will be manually documented in [[PKC]], and all processes and activities drivne by [[Jenkins]], [[Ansible]], and [[Terraform]], will be hyperlinked in specific [[PKC]] pages.
#All actions will be manually documented in [[PKC]], and all processes and activities drivne by [[Jenkins]], [[Ansible]], and [[Terraform]], will be hyperlinked in specific [[PKC]] pages.

Revision as of 07:37, 24 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 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 drivne 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
7. Boundary Conditions

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