Skip to content

fix dashboard build #499

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 3, 2024
Merged

Conversation

klinch0
Copy link
Contributor

@klinch0 klinch0 commented Dec 3, 2024

Summary by CodeRabbit

  • New Features

    • Enhanced build process for Kubeapps with improved modularity and patch integration.
    • Introduced version specification for Kubeapps builds.
  • Bug Fixes

    • Streamlined plugin build commands for better performance and clarity.
  • Refactor

    • Restructured Dockerfile to utilize different base images and optimize the build stages.

@klinch0 klinch0 requested a review from kvaps as a code owner December 3, 2024 10:20
@dosubot dosubot bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Dec 3, 2024
Copy link
Contributor

coderabbitai bot commented Dec 3, 2024

Walkthrough

The pull request introduces significant changes to the Dockerfile used for building Kubeapps. The base image for the initial build stage has been switched from bitnami/golang:1.23.2 to alpine, and a new argument VERSION has been added to specify the Kubeapps version. The build process now includes the installation of the patch utility and the application of several patches to the source code. The final image stage uses bitnami/minideb:bookworm, and the build commands for certain plugins have been streamlined.

Changes

File Path Change Summary
packages/system/dashboard/images/kubeapps-apis/Dockerfile - Changed base image to alpine for the initial build stage.
- Introduced ARG VERSION for version specification.
- Removed build command for kapp-controller plugin.
- Streamlined build commands for fluxv2, helm, and resources plugins.
- Final image stage uses bitnami/minideb:bookworm and includes necessary plugins and binaries.

Poem

🐇 In the garden of code, changes bloom bright,
With patches and plugins, all set just right.
From alpine we start, with a version in hand,
Building Kubeapps, oh so grand!
A hop and a skip, through Docker we play,
Crafting our future, day by day! 🌼


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (3)
packages/system/dashboard/images/kubeapps-apis/Dockerfile (3)

7-7: Consider making the VERSION argument mandatory

Hardcoding the default value for VERSION to v2.11.0 might lead to unintentional builds of outdated versions if the argument is not overridden during the build process. Consider removing the default value to require explicit specification of the version.


10-10: Verify the integrity of the downloaded source code

To ensure the security and integrity of the source code, consider verifying the checksum of the downloaded tarball before extraction. This can prevent corrupted or tampered files from affecting the build.


15-18: Consider applying patches in a forked repository

Applying patches during the build process can lead to build failures if the upstream source code changes and the patches no longer apply cleanly. It may be more reliable to apply these patches in a forked repository and reference that repository as the build source.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between f73a5a0 and 87c6214.

📒 Files selected for processing (1)
  • packages/system/dashboard/images/kubeapps-apis/Dockerfile (2 hunks)
🔇 Additional comments (3)
packages/system/dashboard/images/kubeapps-apis/Dockerfile (3)

6-6: Verify the suitability of using alpine as the base image

Switching to alpine as the base image in the source stage may lead to missing dependencies required for building or patching. Ensure that all necessary tools are available in alpine, or consider using an image with the necessary build utilities pre-installed.


20-20: Ensure Go version compatibility

The Go version has been changed from 1.23.2 to 1.22.5. Please verify that the source code is compatible with Go 1.22.5 and that downgrading does not introduce any compatibility issues.


22-22: Confirm the use of module files from the source stage

Copying go.mod and go.sum from the source stage means any local modifications in your build context's module files will be ignored. Ensure this is intentional and that you are not missing local dependencies or overrides.

Comment on lines +57 to +58
COPY --from=source /source/pkg pkg
COPY --from=source /source/cmd cmd
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Local code modifications may be ignored due to copying from the source stage

By copying the pkg and cmd directories from the source stage, any local changes in your build context will not be included in the build. If you intend to include local modifications, consider copying these directories from the build context instead.

Copy link
Member

@kvaps kvaps left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Dec 3, 2024
@kvaps kvaps merged commit ba42118 into cozystack:main Dec 3, 2024
1 check passed
klinch0 added a commit to klinch0/cozystack that referenced this pull request Dec 5, 2024
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **New Features**
- Enhanced build process for Kubeapps with improved modularity and patch
integration.
	- Introduced version specification for Kubeapps builds.

- **Bug Fixes**
	- Streamlined plugin build commands for better performance and clarity.

- **Refactor**
- Restructured Dockerfile to utilize different base images and optimize
the build stages.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm This PR has been approved by a maintainer size:M This PR changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants