{"action":"created","issue":{"url":"https://api.github.com/repos/DirectXMan12/k8s-prometheus-adapter/issues/129","repository_url":"https://api.github.com/repos/DirectXMan12/k8s-prometheus-adapter","labels_url":"https://api.github.com/repos/DirectXMan12/k8s-prometheus-adapter/issues/129/labels{/name}","comments_url":"https://api.github.com/repos/DirectXMan12/k8s-prometheus-adapter/issues/129/comments","events_url":"https://api.github.com/repos/DirectXMan12/k8s-prometheus-adapter/issues/129/events","html_url":"https://github.com/DirectXMan12/k8s-prometheus-adapter/issues/129","id":380429303,"node_id":"MDU6SXNzdWUzODA0MjkzMDM=","number":129,"title":"Problem while lauching prometheus and the adapter","user":{"login":"giovannifs","id":6718611,"node_id":"MDQ6VXNlcjY3MTg2MTE=","avatar_url":"https://avatars0.githubusercontent.com/u/6718611?v=4","gravatar_id":"","url":"https://api.github.com/users/giovannifs","html_url":"https://github.com/giovannifs","followers_url":"https://api.github.com/users/giovannifs/followers","following_url":"https://api.github.com/users/giovannifs/following{/other_user}","gists_url":"https://api.github.com/users/giovannifs/gists{/gist_id}","starred_url":"https://api.github.com/users/giovannifs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/giovannifs/subscriptions","organizations_url":"https://api.github.com/users/giovannifs/orgs","repos_url":"https://api.github.com/users/giovannifs/repos","events_url":"https://api.github.com/users/giovannifs/events{/privacy}","received_events_url":"https://api.github.com/users/giovannifs/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-11-13T21:22:04Z","updated_at":"2018-11-14T13:33:29Z","closed_at":null,"author_association":"NONE","body":"Hi folks, \r\n\r\nWe have developed a new scheduler for the kubernetes and used prometheus for keeping customized metrics required for this. By the end of June, we had a kubernetes cluster (version 1.9.6) configured with this new scheduler running and ok. We are trying to deploy a new cluster (also version 1.9.6) but the prometheus pod is going to **CrashLoopBackOff** status.\r\n\r\nWe were using **directxman12/k8s-prometheus-adapter-amd64:latest** image for adapter. We also had tried to use v0.2.1 image, which is the oldest tag (4 months) and closer to the image we used arround 5 months ago, but it does not work too. \r\n\r\nWhen I describe the prometheus pod, the last events are:\r\n\r\n```bash\r\nEvents:\r\n  Type     Reason   Age                From                          Message\r\n  Normal   Pulling  23m (x37 over 2h)  kubelet, kubemaster-giovanni  pulling image \"directxman12/k8s-prometheus-adapter-amd64:latest\"\r\n  Warning  BackOff  3m (x628 over 2h)  kubelet, kubemaster-giovanni  Back-off restarting failed container\r\n```\r\n\r\nWhen I check the log of **cm-adapter** container of prometheus pod, using the command:\r\n\r\n```\r\nkubectl logs -n prom prometheus-$HASH -c cm-adapter\r\n```\r\n\r\nThe output is:\r\n\r\n```bash\r\nunknown flag: --rate-interval\r\nUsage of /adapter:\r\nunknown flag: --rate-interval\r\n      --alsologtostderr                                         log to standard error as well as files\r\n      --authentication-kubeconfig string                        kubeconfig file pointing at the 'core' kubernetes server with enough rights to create tokenaccessreviews.authentication.k8s.io.\r\n      --authentication-skip-lookup                              If false, the authentication-kubeconfig will be used to lookup missing authentication configuration from the cluster.\r\n      --authentication-token-webhook-cache-ttl duration         The duration to cache responses from the webhook token authenticator. (default 10s)\r\n      --authorization-kubeconfig string                         kubeconfig file pointing at the 'core' kubernetes server with enough rights to create  subjectaccessreviews.authorization.k8s.io.\r\n      --authorization-webhook-cache-authorized-ttl duration     The duration to cache 'authorized' responses from the webhook authorizer. (default 10s)\r\n      --authorization-webhook-cache-unauthorized-ttl duration   The duration to cache 'unauthorized' responses from the webhook authorizer. (default 10s)\r\n      --bind-address ip                                         The IP address on which to listen for the --secure-port port. The associated interface(s) must be reachable by the rest of the cluster, and by CLI/web clients. If blank, all interfaces will be used (0.0.0.0 for all IPv4 interfaces and :: for all IPv6 interfaces). (default 0.0.0.0)\r\n      --cert-dir string                                         The directory where the TLS certs are located. If --tls-cert-file and --tls-private-key-file are provided, this flag will be ignored. (default \"apiserver.local.config/certificates\")\r\n      --client-ca-file string                                   If set, any request presenting a client certificate signed by one of the authorities in the client-ca-file is authenticated with an identity corresponding to the CommonName of the client certificate.\r\n      --config string                                           Configuration file containing details of how to transform between Prometheus metrics and custom metrics API resources\r\n      --contention-profiling                                    Enable lock contention profiling, if profiling is enabled\r\n      --discovery-interval duration                             interval at which to refresh API discovery information\r\n      --enable-swagger-ui                                       Enables swagger ui on the apiserver at /swagger-ui\r\n      --http2-max-streams-per-connection int                    The limit that the server gives to clients for the maximum number of streams in an HTTP/2 connection. Zero means to use golang's default.\r\n      --lister-kubeconfig string                                kubeconfig file pointing at the 'core' kubernetes server with enough rights to list any described objects\r\n      --log-flush-frequency duration                            Maximum number of seconds between log flushes (default 5s)\r\n      --log_backtrace_at traceLocation                          when logging hits line file:N, emit a stack trace (default :0)\r\n      --log_dir string                                          If non-empty, write log files in this directory\r\n      --logtostderr                                             log to standard error instead of files (default true)\r\n      --metrics-relist-interval duration                        interval at which to re-list the set of all available metrics from Prometheus (default 10m0s)\r\n      --profiling                                               Enable profiling via web interface host:port/debug/pprof/ (default true)\r\n      --prometheus-auth-config string                           kubeconfig file used to configure auth when connecting to Prometheus.\r\n      --prometheus-auth-incluster                               use auth details from the in-cluster kubeconfig when connecting to prometheus.\r\n      --prometheus-url string                                   URL for connecting to Prometheus. (default \"https://localhost\")\r\n      --requestheader-allowed-names strings                     List of client certificate common names to allow to provide usernames in headers specified by --requestheader-username-headers. If empty, any client certificate validated by the authorities in --requestheader-client-ca-file is allowed.\r\n      --requestheader-client-ca-file string                     Root certificate bundle to use to verify client certificates on incoming requests before trusting usernames in headers specified by --requestheader-username-headers. WARNING: generally do not depend on authorization being already done for incoming requests.\r\n      --requestheader-extra-headers-prefix strings              List of request header prefixes to inspect. X-Remote-Extra- is suggested. (default [x-remote-extra-])\r\n      --requestheader-group-headers strings                     List of request headers to inspect for groups. X-Remote-Group is suggested. (default [x-remote-group])\r\n      --requestheader-username-headers strings                  List of request headers to inspect for usernames. X-Remote-User is common. (default [x-remote-user])\r\n      --secure-port int                                         The port on which to serve HTTPS with authentication and authorization. If 0, don't serve HTTPS at all. (default 443)\r\n      --stderrthreshold severity                                logs at or above this threshold go to stderr (default 2)\r\n      --tls-cert-file string                                    File containing the default x509 Certificate for HTTPS. (CA cert, if any, concatenated after server cert). If HTTPS serving is enabled, and --tls-cert-file and --tls-private-key-file are not provided, a self-signed certificate and key are generated for the public address and saved to the directory specified by --cert-dir.\r\n      --tls-cipher-suites strings                               Comma-separated list of cipher suites for the server. If omitted, the default Go cipher suites will be use.  Possible values: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_RC4_128_SHA,TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_RC4_128_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_RC4_128_SHA\r\n      --tls-min-version string                                  Minimum TLS version supported. Possible values: VersionTLS10, VersionTLS11, VersionTLS12\r\n      --tls-private-key-file string                             File containing the default x509 private key matching --tls-cert-file.\r\n      --tls-sni-cert-key namedCertKey                           A pair of x509 certificate and private key file paths, optionally suffixed with a list of domain patterns which are fully qualified domain names, possibly with prefixed wildcard segments. If no domain patterns are provided, the names of the certificate are extracted. Non-wildcard matches trump over wildcard matches, explicit domain patterns trump over extracted names. For multiple key/certificate pairs, use the --tls-sni-cert-key multiple times. Examples: \"example.crt,example.key\" or \"foo.crt,foo.key:*.foo.com,foo.com\". (default [])\r\n  -v, --v Level                                                 log level for V logs\r\n      --vmodule moduleSpec                                      comma-separated list of pattern=N settings for file-filtered logging\r\n```\r\n\r\nThe cluster that we had working by the end of June also is with this same problem. \r\n\r\nDoes anyone know if the **directxman12/k8s-prometheus-adapter-amd64:latest** image is not compatible with kubernetes v1.9.6 anymore? Or have some idea how to solve this problem?\r\n\r\nAdditionaly, does anyone have a copy of **directxman12/k8s-prometheus-adapter-amd64** image from the end of June that could make available? I could test using an older version of this image.\r\n\r\nWe would appreciate any help."},"comment":{"url":"https://api.github.com/repos/DirectXMan12/k8s-prometheus-adapter/issues/comments/438662936","html_url":"https://github.com/DirectXMan12/k8s-prometheus-adapter/issues/129#issuecomment-438662936","issue_url":"https://api.github.com/repos/DirectXMan12/k8s-prometheus-adapter/issues/129","id":438662936,"node_id":"MDEyOklzc3VlQ29tbWVudDQzODY2MjkzNg==","user":{"login":"metalmatze","id":872251,"node_id":"MDQ6VXNlcjg3MjI1MQ==","avatar_url":"https://avatars1.githubusercontent.com/u/872251?v=4","gravatar_id":"","url":"https://api.github.com/users/metalmatze","html_url":"https://github.com/metalmatze","followers_url":"https://api.github.com/users/metalmatze/followers","following_url":"https://api.github.com/users/metalmatze/following{/other_user}","gists_url":"https://api.github.com/users/metalmatze/gists{/gist_id}","starred_url":"https://api.github.com/users/metalmatze/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/metalmatze/subscriptions","organizations_url":"https://api.github.com/users/metalmatze/orgs","repos_url":"https://api.github.com/users/metalmatze/repos","events_url":"https://api.github.com/users/metalmatze/events{/privacy}","received_events_url":"https://api.github.com/users/metalmatze/received_events","type":"User","site_admin":false},"created_at":"2018-11-14T13:33:29Z","updated_at":"2018-11-14T13:33:29Z","author_association":"CONTRIBUTOR","body":"There was one PR that has introduced new configuration that also removed the flag you're looking for:\r\n\r\nhttps://github.com/DirectXMan12/k8s-prometheus-adapter/pull/46/files#diff-f9233f40676b92d0ec7c641e48a62f5dL79\r\n\r\nIn general I wouldn't advice anyone to run `:latest` container images in their cluster, due to everything moving on, but your configuration being stuck with older version.\r\n\r\nYou are welcome to take a look at the kube-prometheus configuration we have for this adapter:\r\n\r\nhttps://github.com/coreos/prometheus-operator/blob/aecd73e07e67740402196cc20e057f2f1a936224/contrib/kube-prometheus/manifests/prometheus-adapter-deployment.yaml#L17-L23"}}
{"actor":{"display_login":"metalmatze"}}