Skip to content
This repository has been archived by the owner on Apr 2, 2024. It is now read-only.

Latest commit

 

History

History
34 lines (26 loc) · 2.02 KB

File metadata and controls

34 lines (26 loc) · 2.02 KB

KubeCon Day 1 and Using Visual Code with GitHub and getting verified commits to GitHub

Introduction

Today was the first day of KubeCon. And I also figured out how to ensure I have verified badge on my GitHub Commits when I push using Visual Code.

Research

A reference I keep coming back to > kubectl Cheat Sheet Cisco - Kubei : A Kubernetes Runtime Vulnerabilities Scanner Cisco - Mitre ATT&CK framework: What is it and does it work for K8s environment?

From KubeCon Europe, I covered:

  • Keynote
  • Introduction and Deep Dive Into Containerd - Kohei Tokunaga & Akihiro Suda, NTT Corporation
  • Secrets Store CSI Driver: Keeping Secrets Secret - Anish Ramasekar, Microsoft & Tommy Murphy, Google
  • Lessons Learned from Operating ETCD - Pierre Zemb, OVHcloud
  • Writing for Developers: Take your Project Docs to the Next Level - Celeste Horgan, CNCF
  • Ask Me Anything with Joe Beda, Co-creator of Kubernetes (I actually missed this one)

Issues with Visual Code pushing to my repo:

git push origin main:main remote: error: GH007: Your push would publish a private email address.
remote: You can make your email public or disable this protection by visiting:
remote: http://github.com/settings/emails

Fixed with the following in the terminal of Code where I had the push issue:

CMD: git config --global user.email “YOUR_EMAIL_ADDRESS_HERE@users.noreply.github.com” CMD: git commit --amend --reset-author CMD: git push

Maybe better instructions on Stack Overflow here

Try yourself

For getting the verified badge on my commits, I wrote this blog post