vyta

Me as a Lead/Manager

I believe everyone does their best work in an environment of creativity, clarity, and empathy.

• Creative thinking leads to innovation and more importantly, fun. Try the weird thing--Embrace the unknown and find new (strategically and ethically reasonable) paths to solve problems. I got your back.
• Clarity of purpose, plans, and responsibilities are non-negotiables for smooth operations. If at any point things start the get too blurry for comfort, let's get it sorted out.
• Let's not forget that there is indeed a world beyond the team--we are humans dealing with human things, let's treat eachother with kindness and compassion.

What you can expect from me	What I ask from you

vyta

#!/bin/sh -eux

# Docker
sudo apt-get update

sudo apt-get install -y\
    apt-transport-https \
    ca-certificates \
    curl \
    gnupg-agent \

vyta

---
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
networking:
  apiServerAddress: "0.0.0.0"
  apiServerPort: 6443
kubeadmConfigPatchesJSON6902:
- group: kubeadm.k8s.io
  version: v1beta2
  kind: ClusterConfiguration

vyta

---
kind: Cluster
apiVersion: kind.sigs.k8s.io/v1alpha3
nodes:
- role: control-plane
- role: worker

vyta

#!/bin/bash

# The MIT License (MIT)
#
# Copyright (c) 2015 Microsoft Azure
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell

vyta

---
kind: Cluster
apiVersion: kind.sigs.k8s.io/v1alpha3
nodes:
- role: control-plane
- role: worker
- role: worker

vyta

Example of using Azure Monitor to scrape Prometheus metrics from NGINX

NGINX Ingress Controller w/ Helm

1. Enable metrics endpoint:

helm install stable/nginx-ingress --name my-release --set controller.metrics.enabled=true

vyta

Custom VNET Notes

• subnet used for your aks cluster should not overlap with any virtual networks in the environment. This creates a new subnet to be used only by AKS.
• service-cidr:
  • Must not be within the virtual network IP address range of your cluster
  • Must not overlap with any other virtual networks with which the cluster virtual network peers
  • Must not overlap with any on-premises IPs
• dns-service-ip must be within service cidr AND must not use the first address, which is used for the kubernetes.default.svc.cluster.local address
• docker-bridge-address must not be within vnet address space AND must not overlap with any other address ranges in use.

vyta

FYI

• subnet used for your aks cluster should not overlap with any virtual networks in the environment. This creates a new subnet to be used only by AKS.
• service prinicipal must have at least network contributor role to vnet rg
• service-cidr:
  • Must not be within the virtual network IP address range of your cluster
  • Must not overlap with any other virtual networks with which the cluster virtual network peers
  • Must not overlap with any on-premises IPs
  • Must not be within the ranges 169.254.0.0/16, 172.30.0.0/16, or 172.31.0.0/16
• dns-service-ip must be within service cidr AND must not use the first address, which is used for the kubernetes.default.svc.cluster.local address

vyta

Observation

Approximately 10% increase in CPU usage when running containerized application vs running the application directly on the host

Troubleshooting

Tools & Setup:

• Windows Performance Recorder: built-in tool to troubleshoot performance related issues on Windows.