Freaks City

Cloud-native architectures rely heavily on ConfigMaps and Secrets for externalizing application settings. However, modifying these resources does not inherently propagate changes to running containers. Environment variables injected via env remain static until a pod restart. File-based mounts eventually reflect updates but often introduce sligh ...

Core Commands salt - Primary command for executing modules on minions from the master: salt [options] '<target>' <function> [arguments] Example: salt '*' test.ping salt-run - Execute runnner modules on the master: salt-run manage.status # View all minion statuses salt-run manage.down # Show offline minions salt-run manage.u ...

Installation and Startup Download the Nacos binary from the official GitHub releases page and extract it to a convenient location. Inside the extracted directory, conf/application.properties holds default settings, such as the web port (default 8848) wich typically does not need to be changed. Navigate to the bin folder, open a terminal, and ru ...

Nacos Overview Nacos, derived from Dynamic Naming and Configuration Service, is a platform designed to streamline service discovery, configuration management, and governance in cloud-native environments. It simplifies building, delivering, and managing microservice architectures by offering capabilities for dynamic registration, configuration, ...

Nacos functions not only as a service registry but also as a dynamic configuration management server. This capability allows for centralized configuration control, enabling updates to be pushed to multiple services simultaneously without requiring individual modifications or service restarts. When a service starts, it merges local configuration ...

ZooKeeper Watcher Mechanism: Principles and Practical Guide This article explores the ZooKeeper Watcher mechanism, a core component for distributed coordination. It covers fundamental concepts, the publish/subscribe model, workflow, application scenarios, and practical command examples. Background We have three cloud servers (2C4G each) running ...