Robert Kielty RobertKielty

CI Signal Meeting - KubeCon 2022 Contributor Summit

Attendees

@puerco @Claudiu Belu @leonardpahlke @krol @RobKielty @arsh @hsalahi @mkorbi @rajula96reddy

Meeting was attended by a mix of SIG Release CI Signalers, people interested in applying to working on CI Signal and developers

Notes

Robert Kielty gave an overview of the CI Signal Tooling, demoing how to detect flakes using test grid.
- Demo notes
  - Although some training is required, it is not that difficult to find flaky tests using Testgrid. CI Jobs that have flaky tests are highlighted in the summary pages such as https://testgrid.k8s.io/sig-release-master-blocking and https://testgrid.k8s.io/sig-release-master-informing; when you drill down into a job that is flaking, at the time of the meeting say seek out a flaky failure by mousing over a red cell that shows when a test has failed and move to neighboring runs where the test passed. If the k/k git commit is the same for both a passing run and a failing run, congratulations, yo

What's the easiest way to have a family collaborate on capturing their genalogy?

ChatGPT

The easiest way to have a family collaborate on capturing their genealogy would be to use a genealogy software or an online family tree platform that allows multiple users to access and contribute to the family tree. Here are the steps you can follow:

Choose a genealogy software or online family tree platform that best suits your family's needs. Some popular options include Ancestry, FamilySearch, MyHeritage, and Geni.

Invite family members to join the platform and contribute to the family tree. Provide them with instructions on how to add information and attach relevant documents, such as birth certificates and census records.

Set up a system for communication and collaboration, such as a group chat or email thread, to keep everyone informed of updates and changes made to the family tree.

Dealing with secrets

GNOME comes with libsecret. You can use libsecret to store your git credentials:

sudo apt install libsecret-1-0 libsecret-1-dev libglib2.0-dev
sudo make --directory=/usr/share/doc/git/contrib/credential/libsecret
git config --global credential.helper /usr/share/doc/git/contrib/credential/libsecret/git-credential-libsecret

This is the response to /metrics on GitHub's ARC gha-rs-controller

k get pods | grep gha | awk '{print $1}' k port-forward cncf-gha-controller-gha-rs-controller-798bd5b854-86vmt 8080:8080

HELP certwatcher_read_certificate_errors_total Total number of certificate read errors

TYPE certwatcher_read_certificate_errors_total counter

certwatcher_read_certificate_errors_total 0

HELP certwatcher_read_certificate_total Total number of certificate reads

kube-prometheus-stack

Installs the kube-prometheus stack, a collection of Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.

See the kube-prometheus README for details about components, dashboards, and alerts.

Note: This chart was formerly named prometheus-operator chart, now renamed to more clearly reflect that it installs the kube-prometheus project stack, within which Prometheus Operator is only one component.

	#+TITLE: Create
	#+DESCRIPTION: Secret creation

	#+begin_src bash

	#!/bin/bash -
	#===============================================================================
	#
	# FILE: personal_prow.sh
	#

	#+TITLE: Create
	#+DESCRIPTION: Secret creation

	#+name: secret-setup
	#+begin_src bash :results output :tangle secret-setup.sh :shebang "#!/bin/bash"
	declare -r SECRETS_DIR="$(pwd)/secrets"
	declare -r OAUTH_TOKEN_FILE="${SECRETS_DIR}/gh-oauth-token"
	declare -r HMAC_TOKEN_FILE="${SECRETS_DIR}/hmac-token"


	<html>
	<head>
	<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
	<title>Error 500 clojure.lang.ExceptionInfo: clj-http: status 401 {:cached nil, :request-time 189, :repeatable? false, :protocol-version {:name "HTTP", :major 1, :minor 1}, :streaming? true, :http-client #object[org.apache.http.impl.client.InternalHttpClient 0x7ec1c42a "org.apache.http.impl.client.InternalHttpClient@7ec1c42a"], :chunked? false, :type :clj-http.client/unexceptional-status, :reason-phrase "Unauthorized", :headers {"Access-Control-Expose-Headers" "ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset", "Referrer-Policy" "origin-when-cross-origin, strict-origin-when-cross-origin", "Server" "GitHub.com&quot

	docker run registry.k8s.io/autoscaling/cluster-autoscaler:v1.31.0 /cluster-autoscaler -h
	Usage of /cluster-autoscaler:
	pflag: help requested
	--add-dir-header If true, adds the file directory to the header of the log messages
	--address string The address to expose prometheus metrics. (default ":8085")
	--alsologtostderr log to standard error as well as files (no effect when -logtostderr=true)
	--async-node-groups Whether clusterautoscaler creates and deletes node groups asynchronously. Experimental: requires cloud provider supporting async node group operations, enable at your own risk.
	--aws-use-static-instance-list Should CA fetch instance types in runtime or use a static list. AWS only
	--balance-similar-node-groups

	# Default values for kube-prometheus-stack.
	# This is a YAML-formatted file.
	# Declare variables to be passed into your templates.

	## Provide a name in place of kube-prometheus-stack for `app:` labels
	##
	nameOverride: ""

	## Override the deployment namespace
	##