CI/CD Pipeline Using AWX: Pylon

Kakaopay's SRE team built a control pipeline called Pylon to solve problems such as human error, unnecessary build steps, and lack of deployment history management that occur in legacy deployment methods within physical server environments.

Pylon has a separated structure consisting of CI via Jenkins and CD via AWX. By storing build artifacts in a repository, it prevents redundant builds during rollback or canary deployment, thereby reducing lead time.

Key features are as follows:

• CI/CD separation: Jenkins and AWX permission policies are operated independently, and deployment speed is improved by checking build artifacts.
• Custom functionality: Through a Jenkins Shared Library based on Groovy script, additional actions needed by each development team can be implemented.
• Code-based management: Deployment information is managed as YAML files, minimizing human error that occurs when entering parameters.
• Static analysis integration: It can automatically perform static analysis before deployment by integrating with SonarQube.

AWX, which handles CD, provides visual pipeline management and RBAC (Role-Based Access Control). This strengthens security and facilitates audit trails, enhancing the ability to respond to audits in the financial sector.