<match kubernetes.**>
@id kubernetes_nginx_tag
@type rewrite_tag_filter
@log_level trace
<rule>
key kubernetes_container_name
pattern /^ingress-nginx$/
tag kubernetes.nginx
Just like other cloud providers Google allows for startup scripts. Once nice thing about GCE is you can easily restart your startup script for debugging reasons.
Login and run the following command to restart the startup script.
sudo google_metadata_script_runner --script-type startup --debug
This deployment will run Telegraf on Kubernetes. This will create a single pod configured to receive webhook events from configured repositories.
Dependencies:
- You must be running nginx ingress controller within your cluster.
- Your cluster should be running external dns with a configured domain and zone. This allows for DNS records to be created automatically.
- Certmanager should be used to handle creating TLS certificates.
- You should already or can create the required credentials for your Telegraf input and output endpoints.
Get a list of pods on for each node based on node status that is unschedulable
for i in $(kubectl get nodes -o wide -L my.label/type --field-selector spec.unschedulable=true |sed 1d | awk '{print $1}'); do
kubectl get pods --all-namespaces --field-selector spec.nodeName=${i} -o wide
done
I hereby claim:
- I am bondanthony on github.
- I am bondanthony (https://keybase.io/bondanthony) on keybase.
- I have a public key whose fingerprint is D41B 91E6 A7E5 06B6 8F9E F1B2 3041 BB87 8C89 EF7D
To claim this, I am signing this object:
I struggled to get the right mix of github actions to lint my terraform modules within a monorepo. Here is the configuration I settled on which dynamically creates new jobs based on the data within the project.
I use a module naming pattern of provider-module_name
, which becomes aws-kubernetes
or gcp-gke
.
This information is important because the action executes the following command to create a list of modules.
$(printf '\"%s\"', gcp-* aws-* azure-* | sed 's/,$//')