Issues on extender.md document

[Mia-Dan]

Hello there,

I'm trying to run the guide for using a custom scheduler extender. But still quite confused after 3 days of attempts. Any help is greatly appreciated.

1. The links in this step is broken.

Run Simulator: We have an example [docker-compose.yaml](https://github.com/kubernetes-sigs/kube-scheduler-simulator/blob/master/simulator/docs/example/docker-compose.yaml); you can overwrite the [docker-compose-local.yaml](https://github.com/kubernetes-sigs/kube-scheduler-simulator/blob/master/docker-compose-local.yml) file with this file, but make sure to update the extender's image name there.

I find a compose.local.yml which seems to be the docker-compose.yaml in 0.3.0 branch, from where I find simulator/docs/sample/plugin-extender/docker-compose.yaml.. I edited that file and then overwrite compose.local.yml.

However, it brings a whole lot of
error like compose.local.yml: services.fake-source-cluster.healthcheck Additional property start_interval is not allowed...

2. Also, I'm not sure where the kubeschedulerconfig file should be pasted to, as the compose.local.yml doesn't say anything on its supposed path in volumes.

Those two issues are on both master branch and 0.4.0 release.

Any help on how to deploy the example scheduler extender?

Lots of thanks.

[sanposhiho]

I find a compose.local.yml which seems to be the docker-compose.yaml in 0.3.0 branch, from where I find simulator/docs/sample/plugin-extender/docker-compose.yaml.. I edited that file and then overwrite compose.local.yml.

Yeah, sorry we forgot updating the doc. compose.local.yml should be correct.

compose.local.yml: services.fake-source-cluster.healthcheck Additional property start_interval is not allowe

Check out your docker version. Probably upgrading it would solve the issue.
https://stackoverflow.com/questions/76758501/set-the-start-interval-of-a-healthcheck-in-docker-compose-yml

[Mia-Dan]

Thank you for help, sanposhiho.

After upgrade docker a new error occurs, will return to you about if previous problem solved after solving this one. ;)

docker build -t simulator-frontend ./web/
[+] Building 91.7s (13/20)                                 docker:desktop-linux
...
 => [internal] load metadata for docker.io/library/node:16-alpine          0.0s
...
 => [deps 1/5] FROM docker.io/library/node:16-alpine@sha256:a1f9d027912b5  0.0s
 => => resolve docker.io/library/node:16-alpine@sha256:a1f9d027912b58a7c7  0.0s
 => CACHED [builder 2/5] WORKDIR /app                                      0.0s
 => CACHED [runner 3/9] RUN addgroup -g 1001 -S nodejs                     0.0s
 => CACHED [runner 4/9] RUN adduser -S nuxtjs -u 1001                      0.0s
 => CACHED [deps 2/5] RUN apk update &&     apk upgrade &&     apk add --  0.0s
 => CACHED [deps 3/5] WORKDIR /app                                         0.0s
 => CACHED [deps 4/5] COPY package.json yarn.lock ./                       0.0s
 => ERROR [deps 5/5] RUN yarn install --frozen-lockfile                   91.5s
 => CACHED [builder 3/5] COPY . .                                          0.0s
------
 > [deps 5/5] RUN yarn install --frozen-lockfile:
0.435 yarn install v1.22.19
0.534 [1/4] Resolving packages...
0.902 [2/4] Fetching packages...
72.44 [3/4] Linking dependencies...
...
91.11 gyp http GET https://unofficial-builds.nodejs.org/download/release/v16.20.2/node-v16.20.2-headers.tar.gz
91.11 gyp WARN install got an error, rolling back install
91.11 gyp ERR! configure error
91.11 gyp ERR! stack FetchError: request to https://unofficial-builds.nodejs.org/download/release/v16.20.2/node-v16.20.2-headers.tar.gz failed, reason: getaddrinfo EAI_AGAIN unofficial-builds.nodejs.org
...
91.11 Build failed
------

 5 warnings found (use docker --debug to expand):
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 20)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 21)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 24)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 25)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 26)
Dockerfile:9
--------------------
   7 |     WORKDIR /app
   8 |     COPY package.json yarn.lock ./
   9 | >>> RUN yarn install --frozen-lockfile
  10 |
  11 |     FROM node:16-alpine AS builder
--------------------
ERROR: failed to solve: process "/bin/sh -c yarn install --frozen-lockfile" did not complete successfully: exit code: 1

View build details: docker-desktop://dashboard/build/desktop-linux/desktop-linux/tsezsi513rstm5sncv9g2pc8e
make: *** [Makefile:58: docker_build_front] Error 1

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale