Pipeline AMI Creation

The current clusters are created on marketplace AMIs. The issue with this is if the AMI gets pulled off of the marketplace, the autoscaling group is unable to create new instances. If one node gets bounced, it would cause the other nodes to be overprivisioned and likely cause cluster crashes.

To fix this, we should create our own AMIs for the clusters and control when/how we plan on upgrading the clusters. A project packer AMIs has been created as a copy of the CNAP project. In addition to the hardening they do, we should consider replacing the yum-cron with an update upon creation. This keeps us from implementing untested changes to the k8s environment

Acceptance Criteria:

• Packer can be ran and create/destroy images from a feature branch
• Tags/releases can create permanent images to be utilized by other projects

changed milestone to %2.33.0

added teamPipelines & Infrastructure label

set weight to 5

assigned to @justin.gomez, @julian.hair, and @cshannon

added to epic &321 (closed)

mentioned in issue #2240 (closed)

mentioned in issue #2241 (closed)

added triage-kind label

added triage-priority label

It has been determined that we don't want to maintain our own AMIs, closing this issue.

closed