pipo02mix

apiVersion: v1
kind: Namespace
metadata:
  labels:
    kubernetes.io/metadata.name: sonobuoy
  name: sonobuoy
---
apiVersion: cilium.io/v2
kind: CiliumNetworkPolicy
metadata:

pipo02mix

apiVersion: application.giantswarm.io/v1alpha1
kind: App
metadata:
  name: dev00-tkp-prometheus-blackbox-exporter-app
  namespace: org-shared-clusters
spec:
  catalog: hdi-apps-production-catalog
  extraConfigs:
  - kind: configMap
    name: prom-dev-config

pipo02mix

#!/usr/bin/env bash

set -o errexit
set -o nounset
set -o pipefail


for n s in $(kubectl get secret -A | grep konfigure | awk '{print $1" "$2}') ;do kubectl delete secret $s -n $n ;done

kubectl delete gitrepo -n flux-giantswarm management-clusters-fleet giantswarm-config collection

pipo02mix

#!/usr/bin/env bash

set -eu

# defaulting the context to a blank string just uses the currently configured context
context=${1:-""}

max_number_rev=10
declare -a namespaces=( "kube-system" "giantswarm" )

pipo02mix

{
    "checks": [
        {
            "id": "Qch7DwouX1",
            "name": "Low Utilization Amazon EC2 Instances",
            "description": "Checks the Amazon Elastic Compute Cloud (Amazon EC2) instances that were running at any time during the last 14 days and alerts you if the daily CPU utilization was 10% or less and network I/O was 5 MB or less on 4 or more days. Running instances generate hourly usage charges. Although some scenarios can result in low utilization by design, you can often lower your costs by managing the number and size of your instances.\n<br><br>\nEstimated monthly savings are calculated by using the current usage rate for On-Demand Instances and the estimated number of days the instance might be underutilized. Actual savings will vary if you are using Reserved Instances or Spot Instances, or if the instance is not running for a full day. To get daily utilization data, download the report for this check. \n<br>\n<br>\n<b>Alert Criteria</b><br>\nYellow: An instance had 10% or less

pipo02mix

##
## Configuration settings that directly affect the Velero deployment YAML.
##

# Details of the container image to use in the Velero deployment & daemonset (if
# enabling restic). Required.
image:
  repository: velero/velero
  tag: v1.2.0
  pullPolicy: IfNotPresent

pipo02mix

abi.vsyscall32 = 1
debug.exception-trace = 1
debug.kprobes-optimization = 1
dev.hpet.max-user-freq = 64
dev.scsi.logging_level = 0
dev.tty.ldisc_autoload = 1
fs.aio-max-nr = 65536
fs.aio-nr = 0
fs.binfmt_misc.status = enabled
fs.dentry-state = 316819	296125	45	0	0	0

pipo02mix

# How to use:
# 1) check calico version and uncomment proper image version below. By default for calico 2.6+
# 2) kubectl apply -f calicoctl.yaml
# 3) kubectl exec -ti -n kube-system calicoctl -- /calicoctl get nodes

apiVersion: v1
kind: Pod
metadata:
  name: calicoctl
  namespace: kube-system

pipo02mix

129.70.132.34
138.201.64.208
172.217.22.16
209.85.202.82
209.85.203.128
209.85.203.82
213.172.105.106
216.137.61.15
216.137.61.74
216.58.198.80

pipo02mix

apiVersion: v1
kind: ConfigMap
metadata:
  name: squid-acl
data:
  http_url.txt: |
    .com
    .io
    .org
    .co.uk