Skip to content

Instantly share code, notes, and snippets.

View fmuyassarov's full-sized avatar

Feruzjon Muyassarov fmuyassarov

View GitHub Profile
@fmuyassarov
fmuyassarov / 10-crio.conf
Last active February 6, 2025 09:50
cri-o config
[crio.image]
signature_policy = "/etc/crio/policy.json"
[crio.runtime]
default_runtime = "runc"
log_level = "debug"
[crio.runtime.runtimes.crun]
runtime_type = "pod"
runtime_path = "/usr/libexec/crio/crun"
@fmuyassarov
fmuyassarov / ta.log
Created November 19, 2024 19:14
cpu manager (static)
STEP 1/3 — Building Dockerfile: [ttl.sh/ghcr.io/containers/nri-plugins/nri-resource-policy-topology-aware]
Building Dockerfile for platform linux/amd64:
ARG GO_VERSION=1.22
FROM golang:${GO_VERSION}-bullseye AS builder
ARG IMAGE_VERSION
ARG BUILD_VERSION
ARG BUILD_BUILDID
ARG DEBUG=0
@fmuyassarov
fmuyassarov / ta.log
Created November 19, 2024 18:40
no cpu manager
STEP 1/3 — Building Dockerfile: [ttl.sh/ghcr.io/containers/nri-plugins/nri-resource-policy-topology-aware]
Building Dockerfile for platform linux/amd64:
ARG GO_VERSION=1.22
FROM golang:${GO_VERSION}-bullseye AS builder
ARG IMAGE_VERSION
ARG BUILD_VERSION
ARG BUILD_BUILDID
ARG DEBUG=0
@fmuyassarov
fmuyassarov / nrt.yaml
Last active October 25, 2024 09:29
Node Resource Topology (TA policy)
apiVersion: topology.node.k8s.io/v1alpha2
attributes:
- name: TopologyPolicy
value: topology-aware
kind: NodeResourceTopology
metadata:
creationTimestamp: "2024-10-25T09:23:16Z"
generation: 1
name: dev-20241025-074512
resourceVersion: "1054"
#!/bin/bash
ns=${NS:-default}
BLUE='\033[0;34m'
Color_Off='\033[0m'
for pod in $(kubectl -n $ns get pods | tr -s '\t' ' ' |
cut -d ' ' -f1 | grep -v ^NAME | tr -d '"'); do
for ctr in $(kubectl get -n $ns pod $pod -o json |
jq '.spec.containers[].name' | tr -d '"'); do
@fmuyassarov
fmuyassarov / How_to_setup_prow.md
Last active October 2, 2024 23:20
How I set up my Prow with Azure storage

Prow with Azure cloud storage

Recently I had to build a Prow cluster for one of the projects I was working on. Usually you want to configure Prow to store job artifacts in some cloud storage so that people could access those logs later on. In my case, Azure cloud was the only option to go with. Unfortunately, at the time of writing this post Prow doesn't support Azure as storage backed and only GCP or AWS S3.

However, thanks to MinIO, I could build my Prow cluster and still store the job artifacts in Azure storage as I would in GCP or AWS S3. So I wanted to share how I configured my Prow cluster to work with Azure storage.

Note: This is Prow setup in a local test environment. In other words, there is no TLS, cert-manager, ingress controller configuration involved as they would in real setup.

Prerequisites

@fmuyassarov
fmuyassarov / minio.yaml
Last active September 4, 2021 23:05
MinIO deployment
apiVersion: apps/v1
kind: Deployment
metadata:
name: minio
namespace: prow
spec:
selector:
matchLabels:
app: minio
strategy: