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=In preparation to deploy the [[Kubernetes]] version of [[PKC]] deployment.
|context=In preparation to deploy the [[Kubernetes]] version of [[PKC]] deployment.
|goal=Use [[Kuberentes]] 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]]-based workflow for software and content deployment
|criteria=Attain a [[CI/CD]]-based 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].

Revision as of 07:21, 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

In preparation to deploy the Kubernetes version of PKC deployment.

2. Goal

Use Kubernetes as the main deployment and monitoring mechanism for PKC.

3. Success Criteria

Attain a CI/CD-based workflow for software and content deployment

4. Outputs 5. Process 6. Inputs
  1. A fully functional PKC, running content from ROADMAPS.MIT.EDU.

A set of automated and human triggered actions to deploy both software and content.

  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