thikade

# helm get manifest $RELEASE_NAME | yq -N eval '[.kind, .metadata.name] | join("/")' - | sort
helm get manifest $RELEASE_NAME   | yq -N '[.kind,.metadata.name] | join("/") '| sort | \
  while read X; do \
     Y=$(kubectl get $X -o name 2>/dev/null); \
     test $? -eq 0 && Y="OK     " || Y="MISSING"; \
     echo "$Y  $X"; \
  done

# sample output:
MISSING  ConfigMap/elastic-7

thikade

#To Decrypt Jenkins Password from credentials.xml
#<username>jenkins</username>
#<passphrase>your-sercret-hash-S0SKVKUuFfUfrY3UhhUC3J</passphrase>


#go to the jenkins url 
http://jenkins-host/script

#In the console paste the script
hashed_pw='your-sercret-hash-S0SKVKUuFfUfrY3UhhUC3J'

thikade

1. Change apiVersion from:

   - apiVersion: v1

   (or apiVersion: apps.openshift.io/v1)

   to:

thikade

// Example showing how to patch Kubernetes resources.
package main

import (
	"encoding/json"
	"fmt"

	"k8s.io/apimachinery/pkg/runtime/schema"
	types "k8s.io/apimachinery/pkg/types"
	"k8s.io/client-go/dynamic"

thikade

---
apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: etcd-backup
spec:
  schedule: "0 0 * * *"
  jobTemplate:
    spec:
      template:

thikade

How to add more to Git Bash on Windows

Git for Windows comes bundled with the "Git Bash" terminal which is incredibly handy for unix-like commands on a windows machine. It is missing a few standard linux utilities, but it is easy to add ones that have a windows binary available.

The basic idea is that C:\Program Files\Git\mingw64\ is your / directory according to Git Bash (note: depending on how you installed it, the directory might be different. from the start menu, right click on the Git Bash icon and open file location. It might be something like C:\Users\name\AppData\Local\Programs\Git, the mingw64 in this directory is your root. Find it by using pwd -W). If you go to that directory, you will find the typical linux root folder structure (bin, etc, lib and so on).

If you are missing a utility, such as wget, track down a binary for windows and copy the files to the corresponding directories. Sometimes the windows binary have funny prefixes, so

thikade

import jenkins.model.*

def matchedJobs = Jenkins.instance.items.findAll { job ->
    job.name =~ /^OpenShift sample$/
}
    
matchedJobs.each { job ->
  println "jobs: ${job.name}"
  //job.delete()
}

thikade

openshift list all pods and their specs (requests/limits)

oc get pod -o jsonpath='{range .items[*]}{"SPEC:  \n  LIMITS  : "}{.spec.containers[*].resources.limits}{"\n  REQUESTS: "}{.spec.containers[*].resources.requests}{"\n"}{end}'

openshift list all pods and their specs with name (requests /limits)

oc get pod -o jsonpath='{range .items[*]}{"NAME:  "}{.metadata.name}{"\nSPEC:  \n  LIMITS  : "}{.spec.containers[*].resources.limits}{"\n  REQUESTS: "}{.spec.containers[*].resources.requests}{"\n\n"}{end}'

thikade

Squashing Git Commits

The standard way that produces a single commit.

Use merge --squash to squash multiple commits into a single commit (without a merge commit!). Omitting -m at the final commit command will display all commit messages of bugfix branch and lets you edit the new commit message.

Switch to the master branch and make sure you are up to date:

git checkout master && git pull

thikade

• Binary Builds

oc new-build --binary=true --name=ola2 --image-stream=redhat-openjdk18-openshift
oc start-build ola2 --from-file=./target/ola.jar --follow
oc new-app 

• Turn off/on DC triggers to do a batch of changes without spam many deployments