perfectra1n

---

name: golang-k8s-operator description: Use this agent when you need to design, implement, or review Golang-based Kubernetes operators, controllers, or cloud-native applications. This includes creating custom resources (CRDs), implementing reconciliation loops, working with the Kubernetes API, developing operator patterns, or architecting Kubernetes-native solutions in Go. Examples: Context: User needs help creating a Kubernetes operator in Go. user: "I need to create a custom operator that manages database backups in Kubernetes" assistant: "I'll use the golang-k8s-operator agent to help design and implement this backup operator" Since the user needs to create a Kubernetes operator in Go, the golang-k8s-operator agent is the perfect choice for this task. Context: User is working on a Kubernetes controller. user: "Can you help me implement a reconciliation loop for my custom resource?" assistant: "Let me engage the golang-k8s-operator agent to help you im

perfectra1n

Common labels: {"app":"gitea","container":"gitea","instance":"gitea","job":"gitea/gitea","namespace":"gitea","stream":"stdout"}
Line limit: "1000 reached, received logs cover 41.10% (12min 20sec) of your selected time range (30min)"
Total bytes processed: "800  kB"


2024-04-27 09:18:57.837	2024/04/27 16:18:57 ...s/process/manager.go:231:remove() [T] Done 662d2571: GET: /metrics
2024-04-27 09:18:57.837	2024/04/27 16:18:57 ...eb/routing/logger.go:102:func1() [I] router: completed GET /metrics for 10.233.91.187:36298, 200 OK in 28.7ms @ web/metrics.go:16(web.Metrics)
2024-04-27 09:18:57.808	2024/04/27 16:18:57 ...eb/routing/logger.go:47:func1() [T] router: started   GET /metrics for 10.233.91.187:36298
2024-04-27 09:18:57.807	2024/04/27 16:18:57 ...s/process/manager.go:188:Add() [T] Start 662d2571: GET: /metrics (request)
2024-04-27 09:18:55.139	2024/04/27 16:18:55 ...s/process/manager.go:188:Add() [T] Start 662d256f: git(dir:/data/tmp/local-repo/pull.git3944658044): /usr/bin/git -c protocol.version=2 -c creden

perfectra1n

Common labels: {"app":"gitea","container":"gitea","filename":"/var/log/pods/gitea_gitea-557f594dd-cc6fc_cc348c8b-b04f-4689-8609-859e26eafb70/gitea/0.log","instance":"gitea","job":"gitea/gitea","namespace":"gitea","node_name":"newworkernode4","pod":"gitea-557f594dd-cc6fc","stream":"stdout"}
Line limit: "1000 (199 returned)"
Total bytes processed: "26.7  kB"


2024-04-24 21:21:08.939	Permissions: {AccessMode:owner Units:[0xc0063c5680 0xc0063c56e0 0xc0063c5770 0xc0063c5830 0xc0063c58f0 0xc0063c5950 0xc0063c59b0] UnitsMode:map[]}
2024-04-24 21:21:08.939	2024/04/25 04:21:08 ...s/repo_permission.go:140:func1() [T] Permission Loaded for <User 1:perf3ct> in <Repository 663:perf3ct/homelab-ops>:
2024-04-24 21:21:08.934	2024/04/25 04:21:08 models/repo/repo.go:352:LoadUnits() [T] repo.Units, ID=663, Types: [TypeCode, TypeIssues, TypePullRequests, TypeReleases, TypeWiki, TypeProjects, TypePackages]
2024-04-24 21:21:08.899	2024/04/25 04:21:08 ...rvices/auth/basic.go:92:Verify() [T] Basic Authorization: Valid AccessToken f

perfectra1n

Common labels: {"app":"gitea","container":"gitea","filename":"/var/log/pods/gitea_gitea-557f594dd-q564j_2ef69b0f-914d-4745-b07a-b7a8fed35c27/gitea/0.log","instance":"gitea","job":"gitea/gitea","namespace":"gitea","node_name":"newworkernode1","pod":"gitea-557f594dd-q564j","stream":"stdout"}
Line limit: "1000 (397 returned)"
Total bytes processed: "345  kB"


2024-04-24 21:23:30.029	2024/04/25 04:23:30 ...ices/auth/session.go:40:Verify() [T] Session Authorization: Found user[1]
2024-04-24 21:23:30.011	2024/04/25 04:23:30 ...eb/routing/logger.go:47:func1() [T] router: started   POST /perf3ct/homelab-ops/lastcommit/2f01e577990ed14e329cb83de847f92894559296/kubernetes/apps/mariadb-databases/main/bookstack for 10.233.94.136:59240
2024-04-24 21:23:30.010	2024/04/25 04:23:30 ...s/process/manager.go:188:Add() [T] Start 6629dac2: POST: /perf3ct/homelab-ops/lastcommit/2f01e577990ed14e329cb83de847f92894559296/kubernetes/apps/mariadb-databases/main/bookstack (request)
2024-04-24 21:23:11.008	2024/04/25 04:23:11 ...s/proces

perfectra1n

Migrating to new major PostgreSQL version with CNPG

1. Create new cluster with the monolith bootstrap above
2. Cut over all Postgres services after it’s done initializing
3. Wave goodbye and pray for the lost data in the 5 minutes it took to cut over (could’ve cut over earlier, but I was worried it was going to have a stroke when initializing, so I waited)

Create new cluster with the monolith bootstrap above

First, need to create the new cluster, that's going to be replacing the old one, with the bootstrap section being the important one, to yoink all the data from the previous one

perfectra1n

2023/11/16 22:42:51 ...s/process/manager.go:188:Add() [T] Start 65569aeb-31: PUT: /v2/<user>/<repo>/manifests/db5e586 (request)
2023/11/16 22:42:51 ...eb/routing/logger.go:47:func1() [T] router: started   PUT /v2/<user>/<repo>/manifests/db5e586 for 10.233.81.22:48164
2023/11/16 22:42:51 ...eb/routing/logger.go:78:func1() [W] router: failed    PUT /v2/<user>/<repo>/manifests/db5e586 for 10.233.81.22:48164, panic in 521.6ms @ container/container.go:516(container.UploadManifest), err=runtime error: invalid memory address or nil pointer dereference
2023/11/16 22:42:51 ...s/process/manager.go:231:remove() [T] Done 65569aeb-31: PUT: /v2/<user>/<repo>/manifests/db5e586
2023/11/16 22:42:51 ...rs/common/errpage.go:26:RenderPanicErrorPage() [E] PANIC: runtime error: invalid memory address or nil pointer dereference
/usr/local/go/src/runtime/panic.go:914 (0x43ec3e)
/go/src/code.gitea.io/gitea/modules/web/routing/logger_manager.go:116 (0x1aa5068)
/usr/local/go/src/runtime/panic.go:914 (0x43ec3e)
/usr/local/go/src/runtime

perfectra1n

curl -s https://api.github.com/repos/zadam/trilium/releases/latest \
| grep "browser_download_url.*x64-server" \
| cut -d : -f 2,3 \
| tr -d \" \
| wget -qi -

perfectra1n

import argparse
import gitlab
import sys
import log
import requests
import json


"""
MAIN FUNCTIONS

perfectra1n

hashcat (v6.1.1) starting in benchmark mode...

Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.

* Device #1: CUDA SDK Toolkit installation NOT detected.
             CUDA SDK Toolkit installation required for proper device support and utilization
             Falling back to OpenCL Runtime