We cannot run github actions on PRs from first contributor. With prow job, it seems that we can trust PR and run actions with /ok-to-test.

https://github.com/kubernetes/test-infra/blob/master/prow/jobs.md

/kind feature

What type of PR is this?

/kind api-change /kind feature

What this PR does / why we need it:

• Add import/export method on API
  • Add resources service & handler

export

1. Call each List function and return it in json.

import

1. Post data in json.
2. Apply` to each resource.
3. return status 200 code if cuccess.

Which issue(s) this PR fixes:

Fixes #28

Special notes for your reviewer:

Please review the sections I commented on.

/label tide/merge-method-squash /label do-not-merge/work-in-progress /hold

Hi, I am new to this project (from scheduling-plugin sig). I learned about the kube-scheduler-simulator. In my option, this simulator only simulate pods scheduling process in a new simulation cluster, which means it can't simulate a real cluster for now(e.g production environment) . Is it possible to simulate pods in an already exist environment? I am interesting in contributing to this project, maybe I need to learn more details about it.

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR tries to extend the simulator apiserver to accept CRDs, this is useful because some scheduler-plugins uses CRDs. https://github.com/kubernetes-sigs/kube-scheduler-simulator/issues/77

Additionally, we can directly use the Kubernetes/api-server/createServerChain method to reduce the burden of maintaining API code.

This is a PR spawned from a discussion in PR #113

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

After this extension, user can use kubectl to apply CRDs.

/label tide/merge-method-squash

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Fix lint issues on frontend.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

/label tide/merge-method-squash

What type of PR is this?

/kind documentation

What this PR does / why we need it:

As part of this PR, we are adding documentation for environment variables that are used to configure kube-scheduler-simulator

Which issue(s) this PR fixes:

Fixes #106

Special notes for your reviewer:

/label tide/merge-method-squash

Added Service Layer Interface, Service, Handler, DI to container, as well as the handler and paths to the server. Can I have some guidance on how to test and possible next steps? Thank you

What type of PR is this?

/kind feature

What this PR does / why we need it:

• Implement import/export button on web.
• follow import/export API that implemented on PR #64

Which issue(s) this PR fixes:

Fixes #28

Special notes for your reviewer:

• This PR is related to PR #64 and is including that commit.
• Currently, the basic import/export function be working.

/label tide/merge-method-squash /hold

/kind feature /cc @adtac /cc @Huang-Wei /cc @alculquicondor /assign

Hi team.

what want to do

add images for backend/frontend to k8s.gcr.io

• create PR on kubernetes/k8s.io
  • this doc helps us: https://github.com/kubernetes/k8s.io/tree/main/k8s.gcr.io
  • (like this pr?: https://github.com/kubernetes/k8s.io/pull/1431/files)
• push images with cloudbuild
  • this doc helps us: https://github.com/kubernetes/test-infra/blob/master/config/jobs/image-pushing/README.md

why

Now, when users want to use the simulator, they have to clone this repo, build it and run it(on docker or local). This is a little inconvenient because it will take them a lot of time to build frontend/backend (maybe because of some huge dependencies).

So it is great if we can provide images for backend/frontend so that users can only have to run these images. wdyt?

Question

• Are there any requirements for creating the image?
• Do we need to get someone's approval to create images?

I cannot find anything about these in documentations.

Currently, the simulator only supports default plugins. But some users may want to try their custom plugins on the simulator.

• Describe in the documentation how to add a custom plugin to the simulator.
• Add some functions(or some option?) to register the custom plugins

/assign

What type of PR is this?

/kind feature

What this PR does / why we need it:

• Reorganization of the directories of some current resources List components.
• Implement DataTable on web UI. This table view is switchable to the current resources list view.
  • This is an alpha feature. It will be enabled if the ALPHA_TABLE_VIEWS environment value is 1.
• simple searching.
• sorting.
• clickable to edit and delete.

Which issue(s) this PR fixes:

Fixes #96

Special notes for your reviewer:

Samples

clickable

/label tide/merge-method-squash

Closes: 109

Adding endpoint /namespaces/:namespace/pods/:name/metadata/annotations/:annotation

This allows fetching of a single annotation from a specific pod in a specific namespace. The path (.../metadata/annotation...) is intended to mirror the apimachinery API to avoid re-inventing especially assuming this might be expanded.

Given the leveraging of apimachinery, it made sense to add some additional endpoints:

• /namespaces/:namespace/pods/:name/metadata/annotations - when no :annotation is added (or is blank) all annotations are returned
• /namespaces/:namespace/pods/:name - pod details are returned for namspace/pod
• /namespaces/:namespace/pods - pod details are returned for all pods in namespace

Unmarshalling of annotations:

Since the specific goal is to help access scheduler-simulator annotations in a usable format, we attempt to unmarshal specific annotations. A specific scheduler-simulator/* annotation will become map[string]map[string]string.

In addition, when :annotation = "scheduler-simulator" or "scheduler-simulator/" we can conclude that all the simulator annotations for this pod should be returned and unmarshalled into map[string]map[string]map[string]string.

Other cases dump all the metadata and do not unmarshal annotations to avoid errors.

Signed-off-by: Mark Sturdevant [email protected]

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

/label tide/merge-method-squash

What type of PR is this?

/area web

What this PR does / why we need it:

Create user config file for web. Refer to #245.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

In the simulator, we just run almost pure kube-apiserver. The simulator doesn't have much controllers, and something seems actually weird to users sometimes. (like some fields in Pods and Nodes don't get changed, etc) And, for example, https://github.com/kubernetes-sigs/kube-scheduler-simulator/issues/243 directly affects the scheduling results, which we must avoid as a simulator.

I feel we can almost resolve them by integrating Kwok which watches Node and Pods and behaves like kubelet. We can expect Pods and Nodes to behave more like a real cluster but without running any real instances or containers.

/kind feature /triage accepted /area simulator /priority important-longterm

Create the component config in simulator.

Signed-off-by: yanghesong [email protected]

What type of PR is this?

/kind feature /kind cleanup /area simulator

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #245

Special notes for your reviewer:

/cc @sanposhiho

I propose a new feature benchmarker idea based on MetricsCollector #246. In the proposal of the collector, the only responsibility was to collect metrics. This is to provide a way to access metrics not only from scenarios but also from general tools.

Therefore, the Benchmarker aims to make benchmark tests easily executable by having the Scenario and the Collector work together.

It would be nice if it could also work well with KEP-184:scheduler-simulation.

Relates: #167