Manoj Badam manojbadam

kubectl create serviceaccount --namespace kube-system tiller
kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller
kubectl patch deploy --namespace kube-system tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}'

How IAM Role works in AWS

IAM Roles are very useful feature in AWS, it provides an easier and secure way to communicate between two resources in AWS. If there is no IAM role in AWS, then we would be needing AWS IAM Access keys to communicate between the resources, this brings an additional overhead of maintaining/storing the keys securely. IAM roles can be added to few resources like EC2 instance, Lambda etc.. not all resources support adding IAM role. To get deeper view of how IAM roles are work in action, we are taking a simple use case to review.

Use Case: Trying to list contents in s3 bucket from an AWS EC2 instance using EC2 instance IAM Role

Assuming that we have a S3 bucket and few contents in it, we will try to access the S3 contents from an AWS Ec2 instance using the Instance IAM role. EC2 instance role is an IAM role with little more assume permissions.

Lets start by ssh'ing into one of the Ec2 instance.

Cross Namespace Service Monitor in Prometheus Operator

Background: The Prometheus Operator for Kubernetes provides easy monitoring definitions for Kubernetes services and deployment and management of Prometheus instances. ServiceMonitor is a CRD from promethues-operator which declaratively specifies how groups of services should be monitored. The Operator automatically generates Prometheus scrape configuration based on the definition.

By default, Prometheus operator is setup with RBAC which can monitor only pods/Endpoints in monitoring, default and kube-system namespace 1. If we need to monitor pods/services in another namespace we need to create a new role + rolebinding or ClusterRole + ClusterRoleBinding.

Namespace Role

If you want to allow only few namespace to monitor. Its recommended to use Role + RoleBinding Kubernetes Role is a namespaced object, you need to create o

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

	#!/bin/bash
	# Fetch the PID of git commit command just ran
	PID=$(ps aux \| grep "git commit" \| tail -1 \| awk '{print $2}')
	# If unable to fetch the PID, give it another try
	if [[ -z "$PID" ]]; then
	echo "unable to get process id, please try again.."
	exit 1
	fi
	# Fetch the command used
	COMMAND=$(ps -p "$PID" -o args)

	package config

	import (
	"log"
	"time"

	"github.com/imdario/mergo"
	"github.com/kelseyhightower/envconfig"
	)