kubernetes-sigs/kustomize
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/kustomize.git synced 2026-06-12 01:14:22 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

Docs: build site

Browse Source
This commit is contained in:
Phillip Wittrock
2020-07-22 09:27:32 -07:00
parent c6524f984c
commit aa991956ef
130 changed files with 1473 additions and 401 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/zh/blog/index.xml
View File

@@ -23,7 +23,7 @@
<h2 id="summary-of-changes">Summary of changes</h2>
<h3 id="first-release-of-the-go-api-only-module">First release of the Go API-only module.</h3>
<h3 id="first-release-of-the-go-api-only-module">First release of the Go API-only module</h3>
<p>Many of the PRs since the last vrelease were
around restructuring the <em>sigs.k8s.io/kustomize</em>
repository into three Go modules instead of just one.</p>
@@ -257,7 +257,7 @@ resources he needs to declare.</p>
</span><span style="color:#f8f8f8;text-decoration:underline">
</span><span style="color:#f8f8f8;text-decoration:underline"></span><span style="color:#204a87;font-weight:bold">resources</span><span style="color:#000;font-weight:bold">:</span><span style="color:#f8f8f8;text-decoration:underline">
</span><span style="color:#f8f8f8;text-decoration:underline"></span>...<span style="color:#f8f8f8;text-decoration:underline">
</span></code></pre></div><h3 id="resource-and-kustomize-context-matching">Resource and Kustomize Context matching.</h3>
</span></code></pre></div><h3 id="resource-and-kustomize-context-matching">Resource and Kustomize Context matching</h3>
<p>Kustomize is now able to support more aggregation patterns.</p>
<p>If for instance, the top level of kustomization.yaml, is simply
combining sub-components, (as in the following example), Kustomize has improved
@@ -296,7 +296,7 @@ commits) and a <code>v3</code> in Go package paths.</p>
floor on a stable API for <a href="https://kubernetes-sigs.github.io/kustomize/docs/plugins">plugin</a> developers
(both <em>Go</em> plugin developers and <em>exec</em> plugin
developers who happen to use Go).</p>
<h3 id="why-so-soon-after-v210">Why so soon after v2.1.0?</h3>
<h3 id="why-so-soon-after-v210">Why so soon after v2.1.0</h3>
<p>We made a mistake - v2.1.0 should have been
v3.0.0. Per the <a href="https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher">Go modules doc</a> (which have
improved a great deal recently), a release that’s