nitisht

CoreDNS vs kubedns

• On-the-fly DNSSEC signing of served data in CoreDNS.
• kube-dns supports only etcd as the backend, CoreDNS on the other hand has several supported backends.
• kube-dns records do not reflect the state of the cluster. Any query to w-x-y-z.namespace.pod.cluster.local will return an A record with w.x.y.z, even if that IP does not belong to specified namespace or even to the cluster address space. CoreDNS integration offers the option pods verified, which will verify that the IP address w.x.y.z returned is in fact the IP of a pod in the specified namespace.
• Plugin chaining and pluggable architecture makes CoreDNS better suited to adapt to various backends, as compared to kubedns.

CoreDNS plugins

nitisht

Minio Healthcheck

Liveness probe definition

Used to identify situations where server is running but may not behave optimally, i.e. sluggish response or corrupt backend. Such situations can be generally only be fixed after a restart.

Kubernetes kills the container and restarts it in case of liveness probe responding with a failure code.

Readiness probe definition

Used to identify situations where server is not ready to accept requests yet. Such situations are generally recovered after waiting for some time.

nitisht

Delete all the objects in a bucket

while read -r key; do
    mc rm myminio/testb/${key}
done< <(mc ls --json myminio/testb | jq --raw-output '"\(.key)"')

Count objects in a bucket

nitisht

from time import time
from pyspark import SparkContext,SparkConf
import pyrosbag
from functools import partial
import pandas as pd
import numpy as np
from PIL import Image
from io import BytesIO
import rosbag
import cv2