Open
Conversation
f645564 to
353df12
Compare
353df12 to
8cbed3a
Compare
Introduce a CI workflow that validates all kustomization.yaml files in the config directory on pull requests to main. This ensures Kustomize configurations remain valid and buildable.
Enhance the github action workflow with Go build caching, PR triggers for validation builds, and tag-based releases. Images are only pushed on main branch commits and version tags, while PRs only build without pushing. The introduced caching uses the experimental GitHub Actions Cache Exporter Backend to fetch and upload cache blocks for the container image build. Additionally, buildkit cache mounts are being preserved between builds by injecting a temporary container with the cache mount data in the Docker build steps. The procedure is outlined in the Docker Documentation[^1]. Additionally, we don't run any make target during the build process any longer, removing the requirement to install make into the Dockerfile and building the manager binary directly using the appropriate 'go build' command given that required BININFO_ arguments are provided now as build-argument to the docker build context during the workflow execution. [^1]: https://docs.docker.com/build/ci/github-actions/cache/#github-cache.
Introduce a workflow that automatically labels pull requests with size indicators (XS, S, M, L, XL) based on lines changed. This helps reviewers quickly assess PR scope and prioritize reviews.
e5314bc to
756a016
Compare
Introduce a workflow that packages and pushes the Helm chart to ghcr.io as an OCI artifact. Release tags use semantic versioning while branch builds use commit-based versions. PRs only validate the chart package. Additionally, in the published helm chart we intentionally omit any helm dependencies.
Introduce a workflow that runs code generation targets and detects any uncommitted changes. This ensures generated code, docs, charts, and formatting are always up to date in pull requests.
Stop using go-makefile-maker for GitHub Actions workflow generation. With recent additions of custom workflows, maintaining consistency between auto-generated and manually written pipelines became impractical. The effort to update all workflows already requires reviewing each one, so auto-generation provides diminishing value. Additionally, some generated workflows like CodeQL are redundant (enabled at repo level) while others like test-chart required manual modifications anyway. Going forward, all workflows will be manually maintained for this project, providing full control over CI/CD configuration.
756a016 to
5eb7237
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With this PR we stop using go-makefile-maker for GitHub Actions workflow generation. With recent additions of custom workflows, maintaining consistency between auto-generated and manually written pipelines became impractical. The effort to update all workflows already requires reviewing each one, so auto-generation provides diminishing value. Additionally, some generated workflows like CodeQL are redundant (enabled at repo level) while others like test-chart or publishing the docker image to
ghcr.iorequired manual modifications anyway.Going forward, all workflows will be manually maintained for this project, providing full control over CI/CD configuration.