arashkaffamanesh

oc project kubernauts
 
podname=$(oc get pods | grep postgres-$(oc get dc postgres -o jsonpath='{.status.latestVersion}') | grep -v deploy | grep Running | awk '{print $1}')
oc rsh -c postgres $podname
 
OR
 
oc get pods | grep postgres
oc exec -it postgres-pod-name bash
 

arashkaffamanesh

apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    run: alpine
  name: alpine
spec:
  replicas: 1
  selector:
    matchLabels:

arashkaffamanesh

cattle-aws:
   request_spot_instances: false
   spot_price:
   root_disk_size: 20
   iam_instance_profile_name: "rancher-controlplane-role"
   iam_instance_profile_worker: # specify if overlap_cp_etcd_worker is false and existing_vpc is true
   rancher_cluster_name: "cattle-aws-cluster"
   rancher_api_url: "https://rancher.xyz.com/v3"
   rancher_access_key:
   rancher_secret_key:

arashkaffamanesh

export TF_VAR_rancher_access_key=token-xyz123
export TF_VAR_rancher_secret_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
export TF_VAR_AWS_ACCESS_KEY_ID=xxxxxxxxxxxxxxxxxx
export TF_VAR_AWS_SECRET_ACCESS_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxx
export TF_VAR_AWS_DEFAULT_REGION=eu-central-1
export AWS_DEFAULT_REGION=eu-central-1
export AWS_ACCESS_KEY_ID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
export AWS_SECRET_ACCESS_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

arashkaffamanesh

apiVersion: v1
kind: Service
metadata:
  name: kafka-topics
  namespace: aceme-confluent-dev # change it
  labels:
    app.kubernetes.io/component: kafka-topics
spec:
  ports:
  - port: 8082

arashkaffamanesh

apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    run: utils
  name: utils
spec:
  replicas: 1
  selector:
    matchLabels:

arashkaffamanesh

Q: Is it possible to create a custom role, where a non-admin user which has only view rights to run “oc rsh” command to only a certain pod or in a project to all pods?
A: you can define a custom role which allows only rsh permission (pods/exec):

create a yaml file like this: my-custom-role.yaml

```
apiVersion: authorization.openshift.io/v1
kind: ClusterRole
metadata:
  name: rsh-pod

arashkaffamanesh

alias util='kubectl get nodes --no-headers | awk '\''{print $1}'\'' | xargs -I {} sh -c '\''echo {} ; kubectl describe node {} | grep Allocated -A 5 | grep -ve Event -ve Allocated -ve percent -ve -- ; echo '\'''
util

arashkaffamanesh

#!/bin/bash
set -euo pipefail

echo -e "Iterating...\n"

nodes=$(kubectl get node --no-headers -o custom-columns=NAME:.metadata.name)

for node in $nodes; do
  echo "Node: $node"
  kubectl describe node "$node" | sed '1,/Non-terminated Pods/d'

arashkaffamanesh

I've been working with Kafka for over 7 years. I inevitably find myself doing the same set of activities while I'm developing or working with someone else's system. Here's a set of Kafka productivity hacks for doing a few things way faster than you're probably doing them now. 🔥

• Show me all my Kafka topics and their partitions, replicas, and consumers
• Show me the contents of a topic
• Create a Kafka topic
• Produce messages to a Kafka topic
• Validate the schema of messages before producing to a topic
• Do all of this at a distance

Get the tools