telnet 192.168.1.128 8102
Use cmd
+ alt
+ 6
to stop transmission, q(uit)
to exit telnet
.
telnet 192.168.1.128 8102 >> EOF
PO
EOF
#!/bin/sh | |
# based on https://gist.github.com/ipedrazas/9c622404fb41f2343a0db85b3821275d | |
# delete all evicted pods from all namespaces | |
kubectl get pods --all-namespaces | grep Evicted | awk '{print $2 " --namespace=" $1}' | xargs kubectl delete pod | |
# delete all containers in ImagePullBackOff state from all namespaces | |
kubectl get pods --all-namespaces | grep 'ImagePullBackOff' | awk '{print $2 " --namespace=" $1}' | xargs kubectl delete pod | |
# delete all containers in ImagePullBackOff or ErrImagePull or Evicted state from all namespaces |
last update: Dec 4, 2020
import React, { Component, } from 'react'; | |
import { View, Text, TouchableOpacity, FlatList, ListItem, Image, TextInput, Dimensions, | |
Animated, StyleSheet, SectionList, PanResponder, PixelRatio, ScrollView } from 'react-native'; | |
import sectionListGetItemLayout from 'react-native-section-list-get-item-layout' | |
var { height, width } = Dimensions.get('window') | |
/* this component is re-used between displaying the friends/groups and being able to pick them in metoo posts, so there are a few different if statements that |
Cross posted from blog.n1analytics.com
At N1 Analytics we use Kubernetes for running experiments, continuous integration testing and deployment. In this post I document setting up a Kubernetes cluster to automatically provision TLS certificates from Let's Encrypt using Jetstack's Certificate Manager, the helm package manager and the nginx-ingress controller.
I wrote this after migrating our cluster from traefik to use cert manager and nginx-ingress. The end state will be one where we can create Kubernetes ingress with a TLS certificate with only a set of annotations in the respective helm template.
I'm going to assume some background knowlege for this post, if you haven't heard of [Let's Encrypt](https://letsencrypt.org/abou
steps: | |
# build steps | |
- name: 'gcr.io/cloud-builders/docker' | |
args: ['pull', 'gcr.io/$PROJECT_ID/project:latest'] | |
- name: 'gcr.io/cloud-builders/docker' | |
args: [ 'build', '--cache-from', 'gcr.io/$PROJECT_ID/project:latest', '-t', 'gcr.io/$PROJECT_ID/projetc:latest', '-t', 'gcr.io/$PROJECT_ID/project', '.' ] | |
- name: 'gcr.io/cloud-builders/docker' | |
args: [ 'tag', 'gcr.io/$PROJECT_ID/project', 'gcr.io/$PROJECT_ID/project:stable-v-$TAG_NAME'] |
#!/usr/bin/env bash | |
cd `dirname $0`/../.. | |
set -e | |
IMAGE_NAME=eu.gcr.io/${PROJECT_ID}/${REPO_NAME}/$1 | |
# Use multiple cache sources that make sense in given context. | |
# This setup is good for pull-request based CI, as most branches | |
# are based on master branch, each commit has a high chance | |
# to hit the cache of it's direct parent. |
kubectl get pods | grep Evicted | awk '{print $1}' | xargs kubectl delete pod |