Praveen Kumar praveenkumar

I use these ansible scripts (see also) to bring up kubernetes clusters, on centos and fedora. The scripts are awesome, but they put selinux into permissive mode, because, "tokens and selinux don't work together."

That's unfortunate, because one of the main things I'm doing when I turn up a kubernetes cluster is bug-hunting, and selinux can be a source of bugs.

I commented out the bit that put selinux into permissive mode:

#- name: Set selinux permissive because tokens and selinux don't work together
#  selinux: state=permissive policy={{ ansible_selinux.type }}
# when: ansible_selinux is defined and ansible_selinux.status == "enabled"

Kubectl output options

Let's look at some basic kubectl output options.

Our intention is to list nodes (with their AWS InstanceId) and Pods (sorted by node).

We can start with:

kubectl get no

Comparison of ZSH frameworks and plugin managers

Changelog

update 1: add a FAQ section
update 2: benchmark chart and feature comparison table
update 3:
- improve the table with missing features for antigen
- new zplg times result

TLDR

Writing a Custom Controller: Extending the Functionality of Your Cluster [I] - Aaron Levy(CoreOS): https://youtu.be/_BuqPMlXfpE
Writing Kube Controllers for Everyone - Maciej Szulik, Red Hat (Beginner Skill Level): https://youtu.be/AUNPLQVxvmw
Programming Kubernetes with the Go SDK [I] - Aaron Schlesinger, Deis: https://youtu.be/qiB4RxCDC8o
TGI Kubernetes 007: Building a Controller - Heptio: https://youtu.be/8Xo_ghCIOSY
TGI Kubernetes 008: Continuing the Controller - Heptio: https://youtu.be/fWkK-zsFtlU
TGI Kubernetes 009: Finishing the Controller - heptio: https://youtu.be/wqhKCiGsf1Y
Kubernetes Operators: Managing Complex Software with Software [I] - Josh Wood & Jesus Carrillo: https://youtu.be/cj5uk1uje_Y
Deep Dive: Operator Framework BoF - Diane Mueller & Sebastian Pahl, Red Hat: https://youtu.be/fu7ecA2rXmc

title	Running CoreDNS as a DNS Server in a Container
published	true
description	How to manually configure CoreDNS to serve your own DNS zones and
tags	dns, coredns, container, docker

This article is published at:

dev.to

If you've ever needed to or wanted to set up your own DNS server, then this is for you. I recently found myself in possession of a Raspberry Pi, and instead of relying on my home router for DHCP and DNS, I decided to serve both from containers on the Pi, so I could resolve all of my hosts with their respective names when I VPN back to my network. I intended to have all other requests forwarded to another server that weren't in my local network, but still service local systems with my customized hostnames.

Following steps work for F29 for F31 look here

On the remote host

cat /etc/redhat-release
Fedora release 29 (Twenty Nine)

	#!/boot/bzImage

	# Linux kernel userspace initialization code, translated to bash
	# (Minus floppy disk handling, because seriously, it's 2017.)
	# Not 100% accurate, but gives you a good idea of how kernel init works
	# GPLv2, Copyright 2017 Hector Martin <marcan@marcan.st>
	# Based on Linux 4.10-rc2.

	# Note: pretend chroot is a builtin and affects the current process
	# Note: kernel actually uses major/minor device numbers instead of device name

	package main

	import (
	"crypto/tls"
	"crypto/x509"
	"flag"
	"io"
	"io/ioutil"
	"log"
	"os"

	apiVersion: v1
	items:
	- apiVersion: v1
	kind: ImageStream
	metadata:
	annotations:
	openshift.io/image.dockerRepositoryCheck: 2017-06-28T15:00:23Z
	creationTimestamp: null
	generation: 2
	labels:

	# These have to be extracted from the qcow2 image
	# TODO: Provide these via docker image?
	KERNEL="vmlinuz-3.10.0-862.14.4.el7.x86_64"
	INITRD="initramfs-3.10.0-862.14.4.el7.x86_64.img"

	# This is where the magic happens
	#
	# To change the ignition (node type), you can use 'bootstrap', 'master' or 'worker'
	# coreos.config.url=http://192.168.0.168:8080/bootstrap.ign
	#