Skip to content

feat: add mutli-arch Dockerfile#66

Merged
k8s-ci-robot merged 1 commit intokubernetes-sigs:mainfrom
manzil-infinity180:new-dockerfile
Aug 26, 2025
Merged

feat: add mutli-arch Dockerfile#66
k8s-ci-robot merged 1 commit intokubernetes-sigs:mainfrom
manzil-infinity180:new-dockerfile

Conversation

@manzil-infinity180
Copy link
Member

@manzil-infinity180 manzil-infinity180 commented Aug 21, 2025

fixes #5

Added dockerfile and docker-compose.yaml file

did some changes to rollup.config.js to replaces process.env.* during the build step.

  • added .env into.gitignore
  • added docs for build & run the testgrid

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 21, 2025
@k8s-ci-robot
Copy link
Contributor

Hi @manzil-infinity180. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Aug 21, 2025
@manzil-infinity180 manzil-infinity180 marked this pull request as draft August 21, 2025 19:40
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 21, 2025
- "8080:80"
environment:
# - API_HOST=testgrid-data.k8s.io
- API_HOST=host.docker.internal
Copy link
Member Author

Choose a reason for hiding this comment

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

:(

@manzil-infinity180
Copy link
Member Author

Need to test once for the local fake JSON and then it is good to go for review

@manzil-infinity180 manzil-infinity180 marked this pull request as ready for review August 22, 2025 16:58
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 22, 2025
@manzil-infinity180
Copy link
Member Author

Hi @ameukam @michelle192837
Could you please take a look at this PR?
Thanks

@ameukam
Copy link
Member

ameukam commented Aug 22, 2025

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 22, 2025
@manzil-infinity180
Copy link
Member Author

/retest

@ameukam
Copy link
Member

ameukam commented Aug 23, 2025

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 23, 2025
@ameukam
Copy link
Member

ameukam commented Aug 23, 2025

The mechanics of building and pushing to a community-owned Docker repository are not trivial.
I'll take care of that.

A follow-up would be to have A Github Action that trigger a build (without push) of the Dockerfile.
@michelle192837 WDYT ?

Copy link
Contributor

@michelle192837 michelle192837 left a comment

Choose a reason for hiding this comment

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

I have a bunch of writing nitpicks but otherwise this looks fine to me!

web/README.md Outdated

## Build & Run with Docker

- `docker compose up --build` Spins up the frontend container. A local `json-server` which serves the data from `src/fake-api/data.json` file. The frontend (via pnpm local-server) connects to it at `http://localhost:3000/`
Copy link
Contributor

Choose a reason for hiding this comment

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

...: Spins...

and

...container, a local...

web/README.md Outdated

- `docker compose up --build` Spins up the frontend container. A local `json-server` which serves the data from `src/fake-api/data.json` file. The frontend (via pnpm local-server) connects to it at `http://localhost:3000/`

- If you want to external k8s Testgrid API instance - actual data. Uncomment the args from the `Dockerfile`. It is need on the build time, thats why we are passing inside the Dockerfile. You can visit on the `localhost:8080`
Copy link
Contributor

Choose a reason for hiding this comment

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

If you want to use the external k8s TestGrid API instance with actual data:

web/README.md Outdated
--build-arg API_PORT=80
docker compose up
```
- Option 2: → uncomment the `args:` block in your compose file
Copy link
Contributor

Choose a reason for hiding this comment

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

Option 2: Uncomment...

web/README.md Outdated
- `docker compose up --build` Spins up the frontend container. A local `json-server` which serves the data from `src/fake-api/data.json` file. The frontend (via pnpm local-server) connects to it at `http://localhost:3000/`

- If you want to external k8s Testgrid API instance - actual data. Uncomment the args from the `Dockerfile`. It is need on the build time, thats why we are passing inside the Dockerfile. You can visit on the `localhost:8080`
- Option 1: Using CLI --build-arg
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: Indent both Options 1 and 2?

build:
context: .
dockerfile: Dockerfile
# args:
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: Add a comment here noting when to uncomment (e.g. # Uncomment \args` to use the public TestGrid API.`)

@michelle192837
Copy link
Contributor

The mechanics of building and pushing to a community-owned Docker repository are not trivial. I'll take care of that.

A follow-up would be to have A Github Action that trigger a build (without push) of the Dockerfile. @michelle192837 WDYT ?

Thanks Arnaud!

That sounds fine to me; do we have examples of this from other parts of the project?

@ameukam
Copy link
Member

ameukam commented Aug 25, 2025

The mechanics of building and pushing to a community-owned Docker repository are not trivial. I'll take care of that.
A follow-up would be to have A Github Action that trigger a build (without push) of the Dockerfile. @michelle192837 WDYT ?

Thanks Arnaud!

That sounds fine to me; do we have examples of this from other parts of the project?

You can check this cloudbuild spec as an example.

@michelle192837
Copy link
Contributor

The mechanics of building and pushing to a community-owned Docker repository are not trivial. I'll take care of that.
A follow-up would be to have A Github Action that trigger a build (without push) of the Dockerfile. @michelle192837 WDYT ?

Thanks Arnaud!
That sounds fine to me; do we have examples of this from other parts of the project?

You can check this cloudbuild spec as an example.

Oh yeah that part makes sense, I'm more confused about whether we're using GHA in other parts as opposed to a Prow job. (As far as I'm aware Prow jobs are still the recommendation but if we're using GHA for some things happy to try that out).

@ameukam
Copy link
Member

ameukam commented Aug 25, 2025

The mechanics of building and pushing to a community-owned Docker repository are not trivial. I'll take care of that.
A follow-up would be to have A Github Action that trigger a build (without push) of the Dockerfile. @michelle192837 WDYT ?

Thanks Arnaud!
That sounds fine to me; do we have examples of this from other parts of the project?

You can check this cloudbuild spec as an example.

Oh yeah that part makes sense, I'm more confused about whether we're using GHA in other parts as opposed to a Prow job. (As far as I'm aware Prow jobs are still the recommendation but if we're using GHA for some things happy to try that out).

Apologies! You are right. We should stick to Prow jobs for consistency

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 26, 2025
Copy link
Contributor

@michelle192837 michelle192837 left a comment

Choose a reason for hiding this comment

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

Looks great, thanks! :D

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 26, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: manzil-infinity180, michelle192837

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 26, 2025
@k8s-ci-robot k8s-ci-robot merged commit ad1fd0e into kubernetes-sigs:main Aug 26, 2025
3 checks passed
@manzil-infinity180 manzil-infinity180 deleted the new-dockerfile branch August 26, 2025 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add mutli-arch Dockerfile

4 participants