-
Notifications
You must be signed in to change notification settings - Fork 505
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Soliciting linkerd CI requirements for Inclusive Integration with CNCF Projects #1141
Comments
Hi @hh! I took a crack at documenting linkerd's current ci state, and where we'd like to take it, leveraging CNCF's infrastructure. Let us know if this is the direction you had in mind: cncf/wg-ci#14 |
@siggy Looks like cncf/wg-ci#14 was merged. Should we close this one as well? |
@klingerf sgtm. all linkerd ci-related info for cncf is now at https://github.com/cncf/wg-ci/blob/master/projects/linkerd.mkd |
Tim-Brooks
pushed a commit
to Tim-Brooks/linkerd
that referenced
this issue
Dec 20, 2018
…gs (linkerd#1141) This PR adds a Prometheus stat tracking the number of times TLS config files have been reloaded, and the number of times reloading those files has errored. Signed-off-by: Eliza Weisman <[email protected]>
Tim-Brooks
pushed a commit
to Tim-Brooks/linkerd
that referenced
this issue
Dec 20, 2018
Depends on linkerd#1141. This PR adds a `tls_config_last_reload_seconds` Prometheus metric that reports the last time the TLS configuration files were reloaded. Proof that it works: Started the proxy with no certs, then generated them: ``` ➜ http GET localhost:4191/metrics HTTP/1.1 200 OK content-encoding: gzip content-length: 323 content-type: text/plain date: Mon, 25 Jun 2018 23:02:52 GMT # HELP tls_config_reload_total Total number of times the proxy's TLS config files were reloaded. # TYPE tls_config_reload_total counter tls_config_reload_total{status="io_error",path="example-example.crt",error_code="2"} 9 tls_config_reload_total{status="reloaded"} 3 # HELP tls_config_last_reload_seconds Timestamp of when the TLS configuration files were last reloaded successfully (in seconds since the UNIX epoch) # TYPE tls_config_last_reload_seconds gauge tls_config_last_reload_seconds 1529967764 # HELP process_start_time_seconds Time that the process started (in seconds since the UNIX epoch) # TYPE process_start_time_seconds gauge process_start_time_seconds 1529967754 ``` Started the proxy with certs already present: ``` ➜ http GET localhost:4191/metrics HTTP/1.1 200 OK content-encoding: gzip content-length: 285 content-type: text/plain date: Mon, 25 Jun 2018 23:04:39 GMT # HELP tls_config_reload_total Total number of times the proxy's TLS config files were reloaded. # TYPE tls_config_reload_total counter tls_config_reload_total{status="reloaded"} 4 # HELP tls_config_last_reload_seconds Timestamp of when the TLS configuration files were last reloaded successfully (in seconds since the UNIX epoch) # TYPE tls_config_last_reload_seconds gauge tls_config_last_reload_seconds 1529967876 # HELP process_start_time_seconds Time that the process started (in seconds since the UNIX epoch) # TYPE process_start_time_seconds gauge process_start_time_seconds 1529967874 ``` Signed-off-by: Eliza Weisman <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
[cncf-ci-public] CNCF CI Goals
[cncf-ci-public] Soliciting CI requirements via Project GitHub Issues
This github issue is to provide a highly visible invite to be part of creating a cross-cloud cross-project CI within the diverse software communities of the Cloud Native Compute Foundation.
To fully understand our needs and expectations, some help documenting the current state of the linkerd CI and ongoing requirements of the linkerd community would be useful.
https://github.com/cncf/wg-ci/blob/master/projects/linkerd.mkd
As we collect linkerd and other project CI requirements, we'll use the @cncf/cncf-ci-working-group issue at cncf/wg-ci#12 and encourage you to join the discussion on the cncf-ci Mailing List
The text was updated successfully, but these errors were encountered: