Nikhita Raghunath nikhita

This gist host the sigs.k8s.io/kind README demo.

Check broken links in Kubernetes Community repo

To help the community and make sure that all documentation is up to date and correct, a very important role to play is to make sure all links are working correctly.

To do this, you can use simple tools such as markdown-link-check.

Setup

Install markdown-link-check.

Kubernetes New Comers

Folks new to kubernetes and wanting to contribute to the open source project frequently ask "what should I do". Here is my general advice:

If you have an area of interest/experience/passion, look for a match in the SIG list, engage in a SIG or WG or two via their regular meetings, slack channel, mailing lists, etc. Watch what they’re up to, see where your intents and needs match theirs, and contribute to those where you’re capable.
Consider looking at the overarching topics, like docs / contributor experience / release, as areas to get a broad view of the project and perhaps find contribution possibilities.
Don't aim to boil the ocean with huge initial contributions. Look for basic "chopping wood" and "carrying water" areas to get some initial orientation and make notable contributions to the overall community and project health. You don't yet know what you don't know, so be humble, expect to make mistake

Basics

File descriptors

The bash has three default file descriptors for each process:

Overly aggressive CFS

We're looking at CPU bandwidth control via CFS:

https://www.kernel.org/doc/Documentation/scheduler/sched-bwc.txt

Reproduction program

Program does number of iterations, in each iteration we burn CPU in small chunks until we get 5ms of real time spent. On each iteration we also print how much

A collection of The Morning Paper posts relating to containers, operating systems etc.

In order of first appearance in The Morning Paper.

Overview

This gist is based on the information available at golang/dep, only slightly more terse and annotated with a few notes and links primarily for my own personal benefit. It's public in case this information is helpful to anyone else as well.

I initially advocated Glide for my team and then, more recently, vndr. I've also taken the approach of exerting direct control over what goes into vendor/ in my Dockerfiles, and also work from isolated GOPATH environments on my system per project to ensure that dependencies are explicitly found under vendor/.

At the end of the day, vendoring (and committing vendor/) is about being in control of your dependencies and being able to achieve reproducible builds. While you can achieve this manually, things that are nice to have in a vendoring tool include:



	[merge]
	tool = mymeld
	conflictstyle = diff3

	[mergetool "mymeld"]
	# Shows three-pane merge view with central output directly being the merged file to save
	cmd = $MANISHMELD $LOCAL $BASE $REMOTE --output=$MERGED
	#cmd = meld "$LOCAL" "$BASE" "$REMOTE"

	#!/bin/bash -ex

	rm -rf cache.new
	if [ ! -d cache ]; then
	mkdir cache.new
	pushd cache.new
	for repo in $(ls -1 ../kubernetes/staging/src/k8s.io); do
	git clone [email protected]:kubernetes/${repo}.git
	done
	popd

	#!/usr/bin/env python
	from __future__ import print_function
	import re
	import json
	import argparse
	from collections import defaultdict

	import requests

	parser = argparse.ArgumentParser(