[pull] master from yeasy:master#97
Open
pull[bot] wants to merge 1086 commits into
Open
Conversation
Bumps [commander](https://github.com/tj/commander.js) from 7.2.0 to 14.0.3. - [Release notes](https://github.com/tj/commander.js/releases) - [Changelog](https://github.com/tj/commander.js/blob/master/CHANGELOG.md) - [Commits](tj/commander.js@v7.2.0...v14.0.3) --- updated-dependencies: - dependency-name: commander dependency-version: 14.0.3 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
…14.0.3 chore(deps): bump commander from 7.2.0 to 14.0.3
Bumps the dependencies group with 2 updates: [chalk](https://github.com/chalk/chalk) and [vuepress](https://github.com/vuejs/vuepress/tree/HEAD/packages/vuepress). Updates `chalk` from 4.1.2 to 5.6.2 - [Release notes](https://github.com/chalk/chalk/releases) - [Commits](chalk/chalk@v4.1.2...v5.6.2) Updates `vuepress` from 1.8.2 to 1.9.10 - [Release notes](https://github.com/vuejs/vuepress/releases) - [Changelog](https://github.com/vuejs/vuepress/blob/master/CHANGELOG.md) - [Commits](https://github.com/vuejs/vuepress/commits/v1.9.10/packages/vuepress) --- updated-dependencies: - dependency-name: chalk dependency-version: 5.6.2 dependency-type: direct:development update-type: version-update:semver-major dependency-group: dependencies - dependency-name: vuepress dependency-version: 1.9.10 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
…es-8b11ed37b5 chore(deps): bump the dependencies group with 2 updates
The cAdvisor compose examples in 19.3.3 use `privileged: true`, which contradicts the minimum-privilege / cap_drop=all guidance in chapter 18. Add an explicit trade-off note before the first cAdvisor snippet explaining the inconsistency and pointing to 18.4 for capability-based hardening alternatives (cap_add: [SYS_ADMIN] + device_cgroup_rules instead of full privileged mode). This addresses the Round 1 review finding about pedagogical conflict between the monitoring and security chapters.
…ted) The "节点周期" subsection listed `Pending`/`Running`/`Terminated` as node phases, but those are **Pod** phases (pod.status.phase). Kubernetes nodes use Conditions (Ready/MemoryPressure/DiskPressure/PIDPressure) not phases; there is no "Terminated" node state. Removed the misleading subsection and clarified the surviving "节点状态" section with an explicit note distinguishing Pod phases from node conditions, and added the eviction behavior when a node becomes Unknown.
…stry push example - Add OrbStack/Colima comparison table to Mac install chapter (3.7.4) - Add Docker→K8s concept mapping paragraph to Ch13 intro - Add KubeKey/RKE2 deployment tool notes to Ch14 - Add production image checklist to Dockerfile chapter summary - Add build-and-push-to-registry workflow example to GitHub Actions section - Expand Ch18 security summary with dimension table
…n version Docker Engine 29.0.0 was released 2025-11-10 per docs.docker.com release notes, not 2025-11-11 (off by one day). Also bring docker/login-action reference in 18.6 up to v4 to match the 21.2 example (v4 has been current since 2026-03-04).
§7.3 of this book explicitly recommends COPY over ADD for simple
file copies ("在大多数情况下，你应该使用 COPY，而不是 ADD"). The intro
Compose example showed ADD without needing tar extraction or URL
download, contradicting the canonical guidance. Switched to COPY
so the first Dockerfile readers see matches the rule the book
teaches a few chapters later.
The other appendix entries (附录四 best_practices, 附录五 debug, 附录六 resources, 附录八 learning_roadmap) all use H2. glossary.md was the lone H1, which broke the table-of-contents nesting in GitBook. Demoted to H2 to align.
This 7-line file was never in SUMMARY.md and its content is a strict subset of the current 17.1_coreos_intro.md. It looks like a draft that survived the chapter rename to NN.M_topic.md convention. Removed so the directory only contains files reachable from the ToC.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )