DOCSEARCHbyAlgolia
Submit Docs

Yakir's Engineering and DevOps Documentation

website·Indexed 29 days ago

https://yakir.top

A comprehensive technical knowledge base covering cloud platform guides for GCP, AWS, and Aliyun; DevOps command manuals for tools like Ansible, FFmpeg, and ClickHouse; and engineering standards for GitFlow, Docker, and CI/CD workflows via GitHub Actions and GitLab. It also includes a 'Science Surf' section on VPN and proxy technologies such as sing-box, Xray, and WireGuard.

Tokens
167.7K
Snippets
797
Records
1K
Agent score
52%

What's inside Yakir GitBook

  1. Overview of cloud-native observability tools

    Cloud-native observability is achieved through a combination of monitoring, logging, tracing, and visualization tools. Key industry-standard tools include:

    • Metrics & Monitoring: Prometheus (time-series database), VictoriaMetrics (fast Prometheus replacement/long-term store), and Grafana (dashboards).
    • Logging: Fluentd (collection/forwarding), Logstash (processing pipeline), Loki (scalable aggregation), and Elastic (search and analytics).
    • Tracing: Jaeger (microservice monitoring) and OpenTelemetry (vendor-neutral telemetry framework for traces, metrics, and logs).

  3. Overview of containerd container runtime

    containerd is an industry-standard container runtime designed to manage the complete container lifecycle on a host system. Its core responsibilities include image transfer and storage, container execution, supervision, and networking.

  4. Overview of Apache ZooKeeper

    Apache ZooKeeper is a centralized coordination service for distributed systems. It provides primitives for configuration management, naming, distributed synchronization, and group services using a hierarchical key-value namespace (znodes) with strong ordering guarantees. It is commonly used as the coordination backend for systems like Kafka, HBase, and Hadoop.

  5. Overview of CRI-O Container Runtime

    CRI-O is a lightweight container runtime built exclusively to implement the Kubernetes Container Runtime Interface (CRI). It provides a minimal, stable alternative to Docker and containerd. CRI-O is OCI-compatible, supporting runtimes like runc, crun, and Kata Containers. A key characteristic is its version alignment: CRI-O minor versions match the corresponding Kubernetes minor versions (e.g., CRI-O 1.x.y for Kubernetes 1.x.y).

  6. Overview of cert-manager for Kubernetes

    cert-manager is a Kubernetes-native certificate management controller that automates the issuance, renewal, and rotation of X.509 certificates. It supports multiple issuers including Let's Encrypt (ACME), HashiCorp Vault, Venafi, self-signed, and private CAs. It provides declarative TLS configuration for Ingress, Gateway API, and other workloads via three primary Custom Resource Definitions (CRDs): Certificate, Issuer, and ClusterIssuer.

  9. Overview of Service Proxy and Load Balancing Tools

    Service proxies and load balancers are used to route, balance, and secure network traffic. Common industry-standard tools for these tasks include:

    • Envoy: A high-performance edge and service proxy specifically designed for cloud-native applications.
    • HAProxy: A reliable, high-performance TCP/HTTP load balancer and proxy.
    • Nginx: A high-performance web server, reverse proxy, and load balancer.

  10. Overview of Apache Flink features and architecture

    Apache Flink is an open-source, unified stream and batch processing framework providing high-throughput, low-latency processing with exactly-once state consistency.

    Key capabilities include:

    • Unified Stream & Batch: Batch processing is treated as a special case of stream processing.
    • Exactly-Once Semantics: Uses lightweight distributed snapshots (Chandy-Lamport algorithm) for consistent state.
    • Event Time Processing: Supports watermarks and event-time windowing for out-of-order events.
    • Stateful Computation: Built-in state management using backends like RocksDB or HashMaps.
    • Fault Tolerance: Automatic recovery via periodic checkpoints and savepoints.

    Architecture Components:

    • JobManager: Coordinates distributed execution, schedules tasks, triggers checkpoints, and handles failover.
    • TaskManager: Worker processes that execute tasks and manage local state.

  11. Overview of gRPC features and architecture

    gRPC is a high-performance, open-source RPC framework that uses Protocol Buffers (protobuf) as its interface definition language (IDL) and message serialization format. It operates over HTTP/2, enabling multiplexing, header compression, and bidirectional streaming. Key capabilities include strongly-typed interfaces, built-in deadline propagation, interceptors for middleware (logging/auth), and support for multiple languages including Go, Java, Python, C++, Node.js, and Rust.

  12. Overview of Cloud Native Storage solutions for Kubernetes

    Cloud Native Storage provides solutions for managing persistent data within containerized and Kubernetes environments. Key industry-standard tools and specifications include:

    • CSI (Container Storage Interface): The standard specification for exposing storage systems to containerized workloads.
    • MinIO: A high-performance, S3-compatible object storage solution designed for cloud-native workloads.
    • Rook: A storage orchestrator that transforms distributed storage into self-managing services within Kubernetes.
    • Velero: A tool dedicated to the backup and disaster recovery of Kubernetes cluster resources and persistent volumes.