mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-09-17 07:03:31 +00:00
The VS and dot is seprated
Signed-off-by: YuPengZTE <yu.peng36@zte.com.cn>
This commit is contained in:
@@ -590,7 +590,7 @@ renaming parameters seems less likely than changing field paths.
|
||||
|
||||
Openshift defines templates as a first class resource so they can be created/retrieved/etc via standard tools. This allows client tools to list available templates (available in the openshift cluster), allows existing resource security controls to be applied to templates, and generally provides a more integrated feel to templates. However there is no explicit requirement that for k8s to adopt templates, it must also adopt storing them in the cluster.
|
||||
|
||||
### Processing templates (server vs client)
|
||||
### Processing templates (server vs. client)
|
||||
|
||||
Openshift handles template processing via a server endpoint which consumes a template object from the client and returns the list of objects
|
||||
produced by processing the template. It is also possible to handle the entire template processing flow via the client, but this was deemed
|
||||
|
Reference in New Issue
Block a user