Examining X.509 Certificates Embedded in Kubeconfig Files
While exploring some of the intricacies around the use of X.509v3 certificates in Kubernetes, I found myself wanting to be able to view the details of a certificate embedded in a kubeconfig file. (See this page if you’re unfamiliar with what a kubeconfig file is.) In this post, I’ll share with you the commands I used to accomplish this task.
First, you’ll want to extract the certificate data from the kubeconfig file. For the purposes of this post, I’ll use a kubeconfig file named config and found in the .kube subdirectory of your home directory. Assuming there’s only a single certificate embedded in the file, you can use a simple grep statement to isolate this information:
grep 'client-certificate-data' $HOME/.kube/config
Combine that with awk to isolate only the certificate data:
grep 'client-certificate-data' $HOME/.kube/config | awk '{print $2}'
This data is Base64-encoded, so we decode it (I’ll wrap the command using backslashes for readability now that it has grown a bit longer):
grep 'client-certificate-data' $HOME/.kube/config | \
awk '{print $2}' | base64 -d
You could, at this stage, redirect the output into a file (like certificate.crt) if so desired; the data you have is Continue reading



Nyansa’s software platform Voyance collects data from across the network, correlates it, determines patterns and anomalies, and suggests remediation. Its most recent update fixes two known blind spots in the monitoring tool.
VictorOps’ platform for incident management will be integrated with the Splunk machine data platform to enable monitoring, event management, and "ChatOps" for DevOps teams.
Google’s Diane Greene joined Robbins on stage at Cisco Live to talk about the Cisco-Google hybrid cloud that is currently available to a handful of cloud customers for refinement.
The support comes from an ingress controller that can automatically provision application delivery configuration and policies for a container.