Skip to content

Instantly share code, notes, and snippets.

View gunjan5's full-sized avatar
🐥
why isn't there a dinosaur emoji here??!?!?!?!

Gunjan "Grass-fed Rabbit" Patel gunjan5

🐥
why isn't there a dinosaur emoji here??!?!?!?!
View GitHub Profile
@gunjan5
gunjan5 / private-gke.md
Created April 22, 2021 18:55 — forked from pydevops/private-k8s.md
kubectl private GKE cluster via Cloud IAP

I'll be doing an Advanced Microservices workshop on Sept 5th & 6th This is the second course in the series. First one is the Kubernetes Intro to Advanced workshop

Here is a rough syllabus for the training (subject to change):

Day 1

Intro

  • What are microservices
  • Quick 101 on containers with a demo
apiVersion: v1
kind: Service
metadata:
name: redis-master
labels:
app: redis
tier: backend
role: master
spec:
#type: LoadBalancer

I will be doing a 2 part workshop on Container/Kubernetes. March 2nd and March 9th. Here is what I'm planning to cover. Time: 12:00pm to 3pm (3/2, and 3/9) Registration: www.npu.edu/news/containerMarch2019

Workshop (Day 1 - Basics) March 2nd

Overview (How we got here): [20 min]

  • Story of a web dude (how a monolith service is managed)
@gunjan5
gunjan5 / Go (Golang) Training Syllabus.md
Last active March 1, 2024 14:05
Go (Golang) Training Syllabus

I'm doing a Go training on January 10th 9:30am to 4pm. Here is roughly what I'm planning to cover.

This is a project driven hands on training, so we will be building a project to learn different Go concepts.

Project: a Key Value Database like etcd/consul and a CLI (using gRPC) to interact with it.

Prerequisite

  • Should've programmed in some language at some point in your life

I'll be doing a Kubernetes Intro to Advanced workshop on Feb 20th 9am to 5pm and Feb 25th 9am to 5pm.

Here is a rough syllabus for the workshop (subject to change):

Overview (How we got here): [20 min]

  • Story of a web dude (how a monolith service is managed)
  • Move from monolith to microservices
  • How is the infrastructure moving with this trend (baremetal -> VM -> containers -> serverless)
  • Where everything is at on the technology curve
{
"ports" : {
"of:0000000000000021/1" : {
"interfaces" : [
{
"ips" : [ "10.2.20.1/16" ],
"vlan" : "-1"
}
]
},
onos:
image: onosproject/onos
container_name: onos
environment:
- "ONOS_APPS=drivers,openflow,segmentrouting"
labels:
- "lab.cord.component=Controller"
restart: always
ports:
- "8181:8181"
#!/usr/bin/env bash
image="gunjan5/onos-sr"
port_str=""
for p in 8181 8101 9876 6653 6633; do
port_str="$port_str -p $p:$p/tcp"
done
echo "Starting docker with publish port list at $port_str"
docker run -itd $port_str $image /bin/bash
{
"ports" : {
"of:0000000badbeef21/7" : {
"interfaces" : [
{
"ips" : [ "1192.168.42.22/16" ],
"vlan" : "-1"
}
]
},