You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/reference/kubectl/kuberc.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,15 +103,17 @@ Specify the built-in command. This includes support for subcommands like `create
103
103
Within a `kuberc`, configuration, command line arguments are termed _flags_ (even if they do not represent a boolean type).
104
104
You can use `flags` to set the default value of a command line argument.
105
105
106
-
If you explicitly specify a flag on your terminal, explicit value will always take precedence over the value you defined in kuberc using `overrides`.
107
-
108
-
{{< note >}}
109
-
You cannot use `kuberc` to override the value of a command line argument to take precedence over what the user specifies on the command line. The term `overrides`
110
-
in this context refers to specifying a default value that is different from the
111
-
compiled-in default value.
112
-
{{< /note >}}
113
-
114
-
#### Example:
106
+
If you explicitly specify a flag on your terminal, explicit value will always take precedence over
107
+
the value you defined in kuberc using `overrides`.
108
+
109
+
{{< note >}}
110
+
You cannot use `kuberc` to override the value of a command line argument to take precedence over
111
+
what the user specifies on the command line. The term `overrides`
112
+
in this context refers to specifying a default value that is different from the
0 commit comments