Add make docker-build in Integration Testing

[kr11]

Summary

This issue proposes the addition of integration tests for the make docker-build command to enhance reliability and detect configuration errors early in the development cycle.

Motivation

Currently, our typical debugging processes involve using make run or debugging via GoLand. However, these methods have significant limitations:

1. RBAC Exposure Issue: The make run command does not reveal issues related to Role-Based Access Control (RBAC). For example, a previous PR addressed this error about horizontalpodautoscalers (PR #72). A similar bug will be addressed in the upcoming PR for podautoscaler_controller - KPA.

2. Detection of Specific Build Issues: Certain problems, such as missing packages or inconsistencies between go.mod and the Dockerfile versions, only become apparent when running make docker-build. An example of this was seen in Pull #92.

These challenges underscore the need for a more robust testing process that can preemptively identify and address potential issues before deployment.

Proposed Change

Some potential ways to solve it include:

• Automated Test Suite: Develop a suite of automated tests that are triggered by changes in the Dockerfile or associated configuration files.
• Continuous Integration Setup: Configure the CI pipeline to execute make docker-build and run tests on every push or pull request to the main branch.

Alternatives Considered

No response

[kr11]

@Jeffwan

[Jeffwan]

@kr11 Let's use [Feat] or something else instead. Let's reserve RFC for some component or architecture changes

[Jeffwan]

This is great suggestion. make docker-build will be included in the CI after #30. make run does have some assumptions. For debugging purpose, I suggest to improve the development documentation if there's additional check we can do. At the same time, we can also do some local integration tests which means running them in local Kubernetes which may help find the issue earlier.

[Jeffwan]

@kr11 docker-build has been added in the PR pipeline here #120 . However, the RBAC can not be tested in this CI yet. I create a new issue #121 to test yaml setup as part of the aibrix integration pipeline.

[Jeffwan]

#120 has been merged and a corresponding fix has been proposed #127. This can be closed now. Feel free to reopen if you think there're unfinished items. @kr11