-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #235 from kruize/mvp_demo
Merge mvp_demo 0.0.8 to main
- Loading branch information
Showing
88 changed files
with
2,909 additions
and
6,639 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
FROM node:16 AS builder | ||
FROM node:22 AS builder | ||
|
||
WORKDIR /app | ||
|
||
|
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,22 +4,51 @@ This repository contains the code for Kruize user interface. The objective behin | |
|
||
This application is built using [Patternfly and React](https://www.patternfly.org/v4/get-started/developers) | ||
|
||
## Before You Start | ||
## Prerequisites | ||
|
||
Kruize UI needs Kruize server running locally. You can setup Kruize [from here](https://github.com/kruize/kruize-demos/tree/main/remote_monitoring_demo). | ||
1. **Kruize Server** | ||
The Kruize UI requires a running instance of the Kruize server. You can set up Kruize using [Kruize Demos](https://github.com/kruize/kruize-demos/tree/main/monitoring/local_monitoring). The setup will also provide you with a link to access the UI. | ||
|
||
2. **Node.js and npm** | ||
Make sure you have the latest stable versions of [`Node.js`](https://nodejs.org/en/) and [`npm`](https://www.npmjs.com/) installed. Check supported versions [here](https://nodejs.org/en/about/releases/). | ||
|
||
Also, make sure you have [`Node.js`](https://nodejs.org/en/) and [`npm`](https://www.npmjs.com/) installed. Check the currently maintained versions at https://nodejs.org/en/about/releases/. | ||
|
||
## Quick Start | ||
|
||
``` | ||
git clone [email protected]:kruize/kruize-ui.git | ||
cd kruize-ui | ||
npm install | ||
export CLUSTER_IP=$(minikube ip) | ||
export KRUIZE_PORT=$(kubectl -n monitoring get svc kruize --no-headers -o=custom-columns=PORT:.spec.ports[*].nodePort 2>/dev/null) | ||
npm run start:dev | ||
``` | ||
For development purposes we prefer running ui locally on minikube or kind as it helps in debugging the ui code. | ||
> **Note**: The main development branch is `mvp_demo`. Please raise your pull requests to this branch. | ||
1. Clone the repository: | ||
|
||
``` | ||
git clone [email protected]:kruize/kruize-ui.git | ||
cd kruize-ui | ||
``` | ||
2. Install dependencies: | ||
|
||
``` | ||
npm install | ||
``` | ||
3. Set the cluster IP: | ||
- For minikube | ||
``` | ||
export CLUSTER_IP=$(minikube ip) | ||
``` | ||
- For KIND | ||
``` | ||
export CLUSTER_IP=$(docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' kind-control-plane) | ||
``` | ||
4. Export the Kruize port: | ||
``` | ||
export KRUIZE_PORT=$(kubectl -n monitoring get svc kruize --no-headers -o=custom-columns=PORT:.spec.ports[*].nodePort 2>/dev/null) | ||
``` | ||
5. Start the development server: | ||
``` | ||
npm run start:dev | ||
``` | ||
## Code Origin | ||
|
Oops, something went wrong.