icy

$ gk8s :euw1 --  fluxctl list-images --k8s-fwd-ns=flux                                                                                                                                        
WORKLOAD                                                        CONTAINER                         IMAGE                                                                    CREATED            
cert-manager:deployment/cert-manager                            cert-manager                      quay.io/jetstack/cert-manager-controller                                                    
                                                                                                  |   canary                                                               10 Feb 20 14:50 UTC
                                                                                                  '-> v0.13.0                                                              21 Jan 20 18:29 UTC
                                                                     

icy

#!/usr/bin/env ruby

# Purpose : Select the objects you want from maninfests,
#           as you may not want to deploy everything.
# Author  : Ky-Anh Huynh
# Date    : 2019-12
# Example :
#
#    helm foo | k8s-select kind=Ingress | kubectl diff -f-
#    helm foo | k8s-select metadata.name=someth | kubectl diff -f-

icy

gk8s_wait_for() {
  retries="$1"; shift
  regex="$1"; shift
  kind="$*"

  set +xe
  echo ":: Wating for expression:"
  echo "::   $kind"
  echo ":://"

icy

#!/usr/bin/env bash

# license : mit
# author  : kyanh-huynh
# purpose : print stats from telegram group exported data

members() {
  grep -Ee '(invited|joined|date details)' messages* \
  |grep -v http \
  |sed -E -e 's#^.+joined.+#foobar.html:joined#g' \

icy

---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: flux
  namespace: demo
  labels:
    name: flux
roleRef:
  apiGroup: rbac.authorization.k8s.io

icy

Links

1. The controller https://github.com/zalando-incubator/kube-ingress-aws-controller
2. External-dns: https://github.com/kubernetes-sigs/external-dns
3. stack creation/update issue: zalando-incubator/kube-ingress-aws-controller#296
4. stack namings: zalando-incubator/kube-ingress-aws-controller#297
5. How it works: https://gist.github.com/icy/9996ef070b0f3c28001f6f2474330c0e

Problems or Goals

icy

resources:
- ../local-end2end
- test-end2end.yaml

namePrefix: RESOURCE_PREFIX_

commonLabels:
  mineHashId: IMAGE_TAG

patches:

icy

#!/usr/bin/env ruby

require 'rubydns'

INTERFACES = [
  [:udp, "0.0.0.0", 53],
  [:tcp, "0.0.0.0", 53],
]

IN = Resolv::DNS::Resource::IN

icy

### A flaw setup of nginx ingress controller

Assuming you have two sites `publicA` and `privateB`, both are running on
the same `k8s` cluster and exposing accesses through nginx ingress controller.
The site `publicA` requires authentication and the site `privateB`
doesn't. Let's consider the following setup

    public ELB/ALB  --> public A with authentication
    private ELB/ALB --> private B

icy

# Purpose: Clean up non-sense filesystem entries from node exporter's metrics
#
#  * Remove all /var/lib/docker, /var/run, /run mount points
#  * Remove all non-ext filesystem
#
# Author : Ky-Anh Huynh
# License: as free as beer, or a MIT
# Efficiency : 108724 metrics --> 1593 metrics

# TODO: support xfs filesystem