Unknown flag: --enable-healthz

[jesuinovieira]

What happened: not able to install volcano after merging pull request #2651

unknown flag: --enable-healthz
Usage of /vc-webhook-manager:
      --add-dir-header                   If true, adds the file directory to the header
      --admission-conf string            The configmap file of this webhook
      --alsologtostderr                  log to standard error as well as files
      --ca-cert-file string              File containing the x509 Certificate for HTTPS.
      --enabled-admission string         enabled admission webhooks, if this parameter is modified, make sure corresponding webhook configurations are the same. (default "/jobs/mutate,/jobs/validate,/podgroups/mutate,/pods/validate,/pods/mutate,/queues/mutate,/queues/validate")
      --ignored-namespaces string        Comma-separated list of namespaces to be ignored by admission webhooks (default "volcano-system,kube-system")
      --kube-api-burst int               Burst to use while talking with kubernetes apiserver (default 100)
      --kube-api-qps float32             QPS to use while talking with kubernetes apiserver (default 50)
      --kubeconfig string                Path to kubeconfig file with authorization and master location information.
      --listen-address string            The address to listen on for the admission-controller-server.
      --log-backtrace-at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
      --log-dir string                   If non-empty, write log files in this directory
      --log-file string                  If non-empty, use this log file
      --log-file-max-size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
      --log-flush-frequency duration     Maximum number of seconds between log flushes (default 5s)
      --logtostderr                      log to standard error instead of files (default true)
      --master string                    The address of the Kubernetes API server (overrides any value in kubeconfig)
      --port int                         the port used by admission-controller-server. (default 8443)
      --scheduler-name stringArray       Volcano will handle pods whose .spec.SchedulerName is same as scheduler-name (default [volcano])
      --skip-headers                     If true, avoid header prefixes in the log messages
      --skip-log-headers                 If true, avoid headers when opening log files
      --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
      --tls-cert-file string             File containing the default x509 Certificate for HTTPS. (CA cert, if any, concatenated after server cert).
      --tls-private-key-file string      File containing the default x509 private key matching --tls-cert-file.
  -v, --v Level                          number for the log level verbosity
      --version                          Show version and quit
      --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
      --webhook-namespace string         The namespace of this webhook
      --webhook-service-name string      The name of this webhook
      --webhook-url string               The url of this webhook
unknown flag: --enable-healthz

What you expected to happen: install without errors

How to reproduce it (as minimally and precisely as possible): install with yaml file, as described in the README

kubectl apply -f https://raw.githubusercontent.com/volcano-sh/volcano/master/installer/volcano-development.yaml

Environment: kind version 0.11.1

• Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.3", GitCommit:"816c97ab8cff8a1c72eccca1026f7820e93e0d25", GitTreeState:"clean", BuildDate:"2022-01-25T21:25:17Z", GoVersion:"go1.17.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-21T23:01:33Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.23) and server (1.21) exceeds the supported minor version skew of +/-1

• OS (e.g. from /etc/os-release):

NAME="Ubuntu"
VERSION="20.04.5 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.5 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

• Kernel (e.g. uname -a):

5.15.0-1022-aws

[wangyang0616]

I just tried it and it didn't reproduce the problem.

May I ask if you have cleared the previous environment of the volcano when you installed the volcano using the volcano-development.yaml file of the master?

[jesuinovieira]

Yes, actually I was installing on a brand new kind cluster 🤔

[fredbjer]

I had this problem too, do you solve it? @jesuinovieira

[wangyang0616]

Yes, actually I was installing on a brand new kind cluster 🤔

The master uploads the image every day at around 00:50 Beijing time. When you deployed at that time, the PR #2651 may have just been integrated, but the master image has not been uploaded yet, which caused this problem.

You can try again, but you need to change the imagePullPolicy in the volcano-development.yaml file from IfNotPresent to Always to avoid the impact of the local cache image

[stale]

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

[stale]

Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗

[ZhangHaoQ]

I had this problem too, do you solve it? @jesuinovieira

[jesuinovieira]

Yep, @wangyang0616's fix did the trick for me