OTUS Publishes Extensive Digest Covering Kubernetes, GitLab CI, DevSecOps and Infrastructure Reliability
OTUS has published a comprehensive digest designed to help IT specialists tackle complex infrastructure tasks that rarely occur in isolation. The material connects issues such as unstable deployments with CI/CD pipelines, container management, secrets handling, performance problems with monitoring and load testing, and network failures with routing, high availability, and Linux configuration.
The digest is structured into several thematic blocks. The first block offers free lessons on Kubernetes, containers and automation. Scheduled sessions include “K8S + Vault — how to obtain secrets?”, “Using GitLab CI for Ansible”, “Docker in production”, “Kubernetes + CI/CD + GitOps”, and “DRY principle in GitLab CI”.
A separate section covers monitoring, logging and performance with lessons on OpenTelemetry, first load testing practices, and comparison of ELK, EFK and Graylog systems.
Network, storage and resilience topics feature lessons on VLAN configuration, RAID5 recovery in Linux, MPLS for corporate networks, and building fault-tolerant clusters using VRRP and HAProxy.
DevSecOps and infrastructure security lessons address business outcomes of DevSecOps projects, practical secure release processes involving SAST, SCA, container scanning and security gates, as well as Linux kernel protection mechanisms.
Additional lessons focus on Linux kernel modules and expert-level PostgreSQL administration for high-load environments.
The article section contains practical guides such as “Your docker-compose.yml will break: 5 settings everyone forgets”, migration from Fail2Ban to CrowdSec for Netbird and Caddy, IP forwarding at L2 and L3 layers, self-service deployment strategies, Kubernetes architecture overview, container security with capabilities, seccomp and AppArmor, L2 loop and broadcast storm detection, CI automation anti-patterns, and a case study of an Intel X710 multicast storm.
For deeper study, OTUS presents advanced courses with entrance testing: “DevSecOps Implementation”, “Observability”, “High-Load Systems Infrastructure”, “Linux Kernel Development”, “PostgreSQL Administration — Expert Level”, “Network Engineer — Advanced”, “Kubernetes Infrastructure Platform”, and “CI/CD with GitLab”.
Related articles
OAuth Authorization Server Built Without Storing User Profiles
The article details the evolution of an OAuth Authorization Server that deliberately avoids storing user profiles, relying instead on external identity providers for authentication. It addresses three core constraints: hundreds of dynamically created isolated APIs, a public SPA client without a BFF, and the inability of resources to query the AS on every request. The design separates concerns so the AS handles only clients, tenants, grants, audiences, scopes, keys, sessions, and token issuance while the Main API owns profiles and roles. Tokens are managed securely inside a Service Worker using a custom FedCM grant, eliminating races across tabs and reducing XSS exposure. The approach minimizes blast radius, simplifies compliance, and keeps the AS replaceable without affecting product domain logic.
Why a 202-Character License Key Uses ECDSA P-256 Instead of Ed25519 or RSA
A developer building offline license verification for a .NET desktop application evaluated Ed25519, RSA, and ECDSA P-256 before selecting the last option. The decision was driven by the requirement for zero external dependencies, keys short enough for manual entry from email, and support for key rotation without breaking existing licenses. Although Ed25519 offers faster verification and a smaller public key, it is absent from System.Security.Cryptography in both .NET 8 and .NET 10, with API approval only targeted for version 11. RSA-2048 produces signatures too long for practical use, resulting in a 571-character Base32 string that users would find cumbersome. ECDSA P-256 with SHA-256 delivers a fixed 64-byte signature that becomes a manageable 202-character key when encoded in Base32, while remaining fully available in the runtime. The article also covers performance measurements, the risks of ECDSA nonce generation, and the deliberate choice of the IEEE P1363 signature format to guarantee fixed-length output.
Pilcrow Publishes Free Comprehensive Guide on Web Authentication
Author Pilcrow has released a detailed, ad-free handbook covering authentication and authorization practices for web applications. The resource draws on personal experience and includes practical examples in JavaScript and Go. It examines password-based methods, email verification, multi-factor authentication, passwordless flows, and passkeys while highlighting associated risks and usability trade-offs. The book also provides in-depth guidance on session management, token security, expiration policies, and email address handling as account identifiers. Recommendations emphasize choosing methods that match application security requirements and user expectations. Additional context is given on OWASP resources and community support channels.
redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem
redb 3.4.0 delivers operational improvements for the .NET integration platform that includes typed storage over Postgres, MSSQL and SQLite, the redb.Route engine modeled after Apache Camel, the Tsak runtime with dashboard and clustering, and redb.Identity for OIDC and OAuth 2.1. The release focuses on post-deployment resilience with replay checkpoints that capture message state at named points inside routes, allowing safe re-execution of downstream steps without duplicating side effects. A shared runtime layer moves framework assemblies into a separate Libs/shared directory so that individual DLLs can be replaced without rebuilding or redeploying the entire Tsak or Identity packages. Secrets are now declared with a [Sensitive] attribute on endpoint options, ensuring URIs containing passwords or keys are sanitized before they reach logs, metrics or health checks. Additional controls include role-based access to management APIs, persistent audit trails and cryptographic signing of dynamically loaded modules. All Pro features remain free on the entire 3.x line with no licensing server required.