blocks|key|4295486|text|执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4295487|export+KUBECONFIG=~/.kube/config:~/someotherconfig+
kubectl+config+view+--flatten|code-block|syntax|javascript|4295488|如果需要，您可以通过管道将其输出到新文件。|4295489|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Do this:

<pre><code>export KUBECONFIG=~/.kube/config:~/someotherconfig 
kubectl config view --flatten
</code></pre>

You can then pipe that out to a new file if needed.

blocks|key|4295545|text|如果要将两个配置文件合并到一个配置文件中|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4295546|我找到了这种方法(不确定这是不是最简单的)|4295547|#+Add+the+two+config+files+to+the+env+var
export+KUBECONFIG=~/.kube/config:~/Desktop/configFile2.yaml

#+Review+that+you+have+two+configurations+in+one+view
kubectl+config+view

#+View+the+raw+config+and+output+to+a+new+file
kubectl+config+view+--raw+>+/tmp/config|code-block|syntax|javascript|4295548|然后将新的配置文件复制到您想要的位置，也不要忘记unset+KUBECONFIG环境变量|offset|length|style|CODE|4295549|entityMap^0|0|0|0|O|G|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

If you want to merge two config files in a single one

I found this way (not sure if this is the simplest)

<pre><code># Add the two config files to the env var
export KUBECONFIG=~/.kube/config:~/Desktop/configFile2.yaml

# Review that you have two configurations in one view
kubectl config view

# View the raw config and output to a new file
kubectl config view --raw &gt; /tmp/config
</code></pre>

Then copy the new config file where you want, also do not forget to <code>unset KUBECONFIG</code> the env variable

blocks|key|4295557|text|如果你发现自己经常这样做...现在还有用于kubectl的krew插件包管理器。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4295558|krew插件"konfig“可以帮助您管理~/.kube/config文件。|4295559|使用konfig插件时，语法将为：|4295560|kubectl+konfig+import+-s+new.yaml|4295561|要安装krew：https://github.com/kubernetes-sigs/krew|4295562|要安装konfig：kubectl+krew+install+konfig|4295563|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/corneliusweig/konfig|1|https://github.com/kubernetes-sigs/krew^0|L|7|T|4|0|0|4|L|E|7|6|0|0|2|6|0|0|X|0|3|4|8|13|1|0|3|6|A|R|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|14|8|@$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|H|3|I|5|6|7|1C|8|@$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1F|8|@$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|1I|8|@$9|1J|A|1K|B|C]]|D|@$9|1L|A|1M|1|1N]]|E|$]]|$1|N|3|O|5|6|7|1O|8|@$9|1P|A|1Q|B|C]|$9|1R|A|1S|B|C]]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1T|8|@]|D|@]|E|$]]]|Q|$R|$5|S|T|U|E|$V|W]]|X|$5|S|T|U|E|$V|Y]]]]

If you find yourself doing this a lot... There is now also the <code>krew</code> plugin package manager for <code>kubectl</code>.
The <code>krew</code> plugin &quot;<a href="https://github.com/corneliusweig/konfig" rel="noreferrer">konfig</a>&quot; can help you manage your <code>~/.kube/config</code> file.
Using the <code>konfig</code> plugin the syntax will be:
<code>kubectl konfig import -s new.yaml</code>
To install <code>krew</code>: <a href="https://github.com/kubernetes-sigs/krew" rel="noreferrer">https://github.com/kubernetes-sigs/krew</a>
To install <code>konfig</code>: <code>kubectl krew install konfig</code>

blocks|key|2183315|text|一次使用多个kubeconfigs|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2183316|有时你有一堆小的kubeconfig文件(例如，每个集群一个)，但你想一次使用所有这些文件，使用kubectl或kubectx等工具，这些工具可以同时处理多个上下文。|BOLD|2183317|为此，您需要一个“合并”的kubeconfig文件。在下面的“合并kubeconfig文件”一节中，我们解释了如何将kubeconfigs合并为一个文件，但也可以在内存中合并它们。|2183318|通过在KUBECONFIG环境变量中指定多个文件，您可以临时将kubeconfig文件缝合在一起，并在kubectl中使用它们。|2183319|#
#+Kubeconfig+in-memory+merge
#
export+KUBECONFIG=file1:file2
kubectl+get+pods+--context=cluster-1
kubectl+get+pods+--context=cluster-2

#
#+For+your+example
#+merging+your+kubeconfig+file+w/+$HOME/.kube/config+(w/+cp+backup)
#
cp+$HOME/.kube/config+$HOME/.kube/config.backup.$(date+%2B%25Y-%25m-%25d.%25H:%25M:%25S)
KUBECONFIG=+$HOME/.kube/config:file2:+kubectl+config+view+--merge+--flatten+>+\
~/.kube/merged_kubeconfig+&&+mv+~/.kube/merged_kubeconfig+~/.kube/config
kubectl+get+pods+--context=cluster-1
kubectl+get+pods+--context=cluster-2|code-block|syntax|javascript|2183320|合并kubeconfig文件|2183321|因为kubeconfig文件是结构化的YAML文件，你不能简单地附加它们来得到一个大的kubeconfig文件，但是kubectl可以帮助你合并这些文件：|2183322|#
#+Merging+your+kubeconfig+file+w/+$HOME/.kube/config+(w/+cp+backup)
#
cp+$HOME/.kube/config+$HOME/.kube/config.backup.$(date+%2B%25Y-%25m-%25d.%25H:%25M:%25S)
KUBECONFIG=$HOME/.kube/config:file2:file3+kubectl+config+view+--merge+--flatten+>+\
~/.kube/merged_kubeconfig+&&+mv+~/.kube/merged_kubeconfig+~/.kube/config
kubectl+get+pods+--context=cluster-1
kubectl+get+pods+--context=cluster-2|2183323|从kubeconfig文件提取上下文|2183324|假设您遵循了合并kubeconfig文件之前的，并在$HOME/.kube/config中合并了一个kubeconfig文件。现在，您希望将集群的信息提取到一个可移植的kubeconfig文件中，该文件只包含连接到该集群所需的部分。|2183325|运行：|2183326|KUBECONFIG=$HOME/.kube/config+kubectl+config+view+\
++++--minify+--flatten+--context=context-1+>+$HOME/.kube/config-context-1

#
#+using+--kubeconfig+flag
#
kubectl+get+pods+--kubeconfig=$HOME/.kube/config-context-1

#
#+or+
#+using+`KUBECONFIG`+environment+variable
#
KUBECONFIG=$HOME/.kube/config-context-1+kubectl+get+pods

#
#+or+
#+keep+using+kubeconfig+file+at+$HOME/.kube/config+(which+has+the+merged+context)
#
kubectl+get+pods+--context=cluster-1|2183327|在此命令中，我们将有关context-1的数据从$HOME/.kube/config提取到config-context-1文件。--minify标志允许我们仅提取关于该上下文的信息，而--flatten标志允许我们保持凭证未经编辑。|2183328|参考文章：+https://ahmet.im/blog/mastering-kubeconfig/|2183329|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ahmetb/kubectx|1|https://ahmet.im/blog/mastering-kubeconfig/^0|6|B|0|8|A|1C|7|1K|7|0|0|D|A|U|G|1M|B|0|3|A|1F|7|V|A|0|0|0|2|A|17|A|1M|7|0|0|0|6|H|1E|A|2C|A|Q|I|0|0|0|B|9|O|I|19|G|1S|8|2K|9|0|0|5|6|17|1|0^^$0|@$1|2|3|4|5|6|7|1J|8|@$9|1K|A|1L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1M|8|@$9|1N|A|1O|B|H]|$9|1P|A|1Q|B|C]]|D|@$9|1R|A|1S|1|1T]]|E|$]]|$1|I|3|J|5|6|7|1U|8|@$9|1V|A|1W|B|H]|$9|1X|A|1Y|B|H]|$9|1Z|A|20|B|H]]|D|@]|E|$]]|$1|K|3|L|5|6|7|21|8|@$9|22|A|23|B|C]|$9|24|A|25|B|C]|$9|26|A|27|B|H]]|D|@]|E|$]]|$1|M|3|N|5|O|7|28|8|@]|D|@]|E|$P|Q]]|$1|R|3|S|5|6|7|29|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|2A|8|@$9|2B|A|2C|B|H]|$9|2D|A|2E|B|H]|$9|2F|A|2G|B|C]]|D|@]|E|$]]|$1|V|3|W|5|O|7|2H|8|@]|D|@]|E|$P|Q]]|$1|X|3|Y|5|6|7|2I|8|@]|D|@]|E|$]]|$1|Z|3|10|5|6|7|2J|8|@$9|2K|A|2L|B|H]|$9|2M|A|2N|B|H]|$9|2O|A|2P|B|H]|$9|2Q|A|2R|B|C]]|D|@]|E|$]]|$1|11|3|12|5|6|7|2S|8|@]|D|@]|E|$]]|$1|13|3|14|5|O|7|2T|8|@]|D|@]|E|$P|Q]]|$1|15|3|16|5|6|7|2U|8|@$9|2V|A|2W|B|C]|$9|2X|A|2Y|B|C]|$9|2Z|A|30|B|C]|$9|31|A|32|B|C]|$9|33|A|34|B|C]]|D|@]|E|$]]|$1|17|3|18|5|6|7|35|8|@$9|36|A|37|B|H]]|D|@$9|38|A|39|1|3A]]|E|$]]|$1|19|3|-4|5|6|7|3B|8|@]|D|@]|E|$]]]|1A|$1B|$5|1C|1D|1E|E|$1F|1G]]|1H|$5|1C|1D|1E|E|$1F|1I]]]]

<h2>Using multiple <code>kubeconfigs</code> at once</h2>

Sometimes you have a bunch of small kubeconfig files (e.g. one per cluster) but you want to use them all at once, with tools like <code>kubectl</code> or <a href="https://github.com/ahmetb/kubectx" rel="noreferrer">kubectx</a> that work with multiple contexts at once.

To do that, you need a “merged” kubeconfig file. In the section "Merging kubeconfig files" below, we explain how you can merge the kubeconfigs into a single file, but you can also merge them in-memory.

By specifying multiple files in <code>KUBECONFIG</code> environment variable, you can temporarily stitch kubeconfig files together and use them all in <code>kubectl</code> .

<pre class="lang-sh prettyprint-override"><code>#
# Kubeconfig in-memory merge
#
export KUBECONFIG=file1:file2
kubectl get pods --context=cluster-1
kubectl get pods --context=cluster-2

#
# For your example
# merging your kubeconfig file w/ $HOME/.kube/config (w/ cp backup)
#
cp $HOME/.kube/config $HOME/.kube/config.backup.$(date +%Y-%m-%d.%H:%M:%S)
KUBECONFIG= $HOME/.kube/config:file2: kubectl config view --merge --flatten &gt; \
~/.kube/merged_kubeconfig &amp;&amp; mv ~/.kube/merged_kubeconfig ~/.kube/config
kubectl get pods --context=cluster-1
kubectl get pods --context=cluster-2
</code></pre>

<h2>Merging kubeconfig files</h2>

Since kubeconfig files are structured YAML files, you can’t just append them to get one big kubeconfig file, but <code>kubectl</code> can help you merge these files:

<pre class="lang-sh prettyprint-override"><code>#
# Merging your kubeconfig file w/ $HOME/.kube/config (w/ cp backup)
#
cp $HOME/.kube/config $HOME/.kube/config.backup.$(date +%Y-%m-%d.%H:%M:%S)
KUBECONFIG=$HOME/.kube/config:file2:file3 kubectl config view --merge --flatten &gt; \
~/.kube/merged_kubeconfig &amp;&amp; mv ~/.kube/merged_kubeconfig ~/.kube/config
kubectl get pods --context=cluster-1
kubectl get pods --context=cluster-2
</code></pre>

<h2>Extracting a context from a kubeconfig file</h2>

Let’s say you followed the before merging kubeconfig files and have a merged kubeconfig file in <code>$HOME/.kube/config</code>. Now you want to extract a cluster’s information to a portable kubeconfig file that only has the parts you need to connect to that cluster. 

Run:

<pre><code>KUBECONFIG=$HOME/.kube/config kubectl config view \
 --minify --flatten --context=context-1 &gt; $HOME/.kube/config-context-1

#
# using --kubeconfig flag
#
kubectl get pods --kubeconfig=$HOME/.kube/config-context-1

#
# or 
# using `KUBECONFIG` environment variable
#
KUBECONFIG=$HOME/.kube/config-context-1 kubectl get pods

#
# or 
# keep using kubeconfig file at $HOME/.kube/config (which has the merged context)
#
kubectl get pods --context=cluster-1
</code></pre>

In this command, we extract data about <code>context-1</code> from <code>$HOME/.kube/config</code> to <code>config-context-1</code> file. The <code>--minify</code> flag allows us to extract only info about that context, and the <code>--flatten</code> flag allows us to keep the credentials unredacted.

ref article: <a href="https://ahmet.im/blog/mastering-kubeconfig/" rel="noreferrer">https://ahmet.im/blog/mastering-kubeconfig/</a>

blocks|key|5712891|text|要动态合并.bashrc中的多个配置文件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5712892|export+KUBECONFIG=/Users/<user>/.kube/config:/Users/<user>/.kube/other.config
source+<(kubectl+completion+bash)|code-block|syntax|javascript|5712893|刷新源文件后，验证：|5712894|kubectl+config+view|5712895|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

To dynamically merge multiple config files in you .bashrc:
<pre><code>export KUBECONFIG=/Users/&lt;user&gt;/.kube/config:/Users/&lt;user&gt;/.kube/other.config
source &lt;(kubectl completion bash)
</code></pre>
After fresh source, verify:
<pre><code>kubectl config view
</code></pre>

blocks|key|2183366|text|如果您使用bash，您可以使用此命令简单地添加配置：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2183367|function+kmerge()+{
+DATE=$(date+%2B"%25Y%25m%25d%25H%25M")
+KUBECONFIG=~/.kube/config:$1+kubectl+config+view+--flatten+>+~/.kube/mergedkub+&&+mv+~/.kube/config+~/.kube/config-$DATE+&&+mv+~/.kube/mergedkub+~/.kube/config
}|code-block|syntax|javascript|2183368|然后使用"kmerge+$newConfigfile“来添加这个。请注意，集群名称等应该与现有配置项不同！|2183369|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

If you use bash you can use this to simply add the configs:
<pre><code>function kmerge() {
 DATE=$(date +&quot;%Y%m%d%H%M&quot;)
 KUBECONFIG=~/.kube/config:$1 kubectl config view --flatten &gt; ~/.kube/mergedkub &amp;&amp; mv ~/.kube/config ~/.kube/config-$DATE &amp;&amp; mv ~/.kube/mergedkub ~/.kube/config
}
</code></pre>
Then just use &quot;kmerge $newConfigfile&quot; to add this.
Be aware the clusternames etc. should be different from existing config entries!

blocks|key|2183380|text|如果希望在~/.kube目录中有一些结构，可以按照这些说明进行操作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2183381|将以下代码片段添加到~/.bashrc|2183382|Add+separately.|unordered-list-item|2183383|
|2183384|call+update_kubeconfigs下的|2183385|2183386|配置文件中，或打开新的~/.kube/config.d+update_kubeconfigs|2183387|2183388|update_kubeconfigs只会查看~/.kube/config.d目录，如果有任何文件比~/.kube/config下的当前配置文件更新，它就会更新它。|2183389|function+update_kubeconfigs()+{
++[+!+-d+"$HOME/.kube/config.d"+]+&&+mkdir+$HOME/.kube/config.d+-p+-v
++#+Will+run+only+if+there+are+new+files+in+the+config+directory
++local+new_files=$(find+$HOME/.kube/config.d/+-newer+$HOME/.kube/config+-type+f+%7C+wc+-l)
++if+[[+$new_files+-ne+"0"+]];+then
++++local+current_context=$(kubectl+config+current-context)+#+Save+last+context
++++local+kubeconfigfile="$HOME/.kube/config"+++++++++++++++#+New+config+file
++++cp+-a+$kubeconfigfile+"${kubeconfigfile}_$(date+%2B"%25Y%25m%25d%25H%25M%25S")"++#+Backup
++++local+kubeconfig_files="$kubeconfigfile:$(ls+$HOME/.kube/config.d/*+%7C+tr+'\n'+':')"
++++KUBECONFIG=$kubeconfig_files+kubectl+config+view+--merge+--flatten+>+"$HOME/.kube/tmp"
++++mv+"$HOME/.kube/tmp"+$kubeconfigfile+&&+chmod+600+$kubeconfigfile
++++export+KUBECONFIG=$kubeconfigfile
++++kubectl+config+use-context+$current_context+--namespace=default
++fi
}

#+This+will+call+each+time+you+source+.bashrc,+remove+it+if+you+want+to+call+it+manually+each+time
update_kubeconfigs|code-block|syntax|javascript|2183390|从~/.kube/confing.d中删除文件将不会再次调用该脚本。同样，正如@rafaelrezend指出的，检查配置文件中的名称冲突，这可能会导致问题。|2183391|Github+gist|2183392|entityMap|0|LINK|mutability|MUTABLE|url|https://gist.github.com/rzjfr/f46e25829492cdf6ce9eb3a28a712acc^0|5|7|0|A|9|0|0|0|5|I|0|0|B|G|S|I|0|0|0|I|M|G|1D|E|0|0|1|H|0|0|B|0|0^^$0|@$1|2|3|4|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1E|8|@$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|1H|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|1I|8|@]|D|@]|E|$]]|$1|M|3|N|5|J|7|1J|8|@$9|1K|A|1L|B|C]]|D|@]|E|$]]|$1|O|3|L|5|6|7|1M|8|@]|D|@]|E|$]]|$1|P|3|Q|5|J|7|1N|8|@$9|1O|A|1P|B|C]|$9|1Q|A|1R|B|C]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1T|8|@$9|1U|A|1V|B|C]|$9|1W|A|1X|B|C]|$9|1Y|A|1Z|B|C]]|D|@]|E|$]]|$1|U|3|V|5|W|7|20|8|@]|D|@]|E|$X|Y]]|$1|Z|3|10|5|6|7|21|8|@$9|22|A|23|B|C]]|D|@]|E|$]]|$1|11|3|12|5|6|7|24|8|@]|D|@$9|25|A|26|1|27]]|E|$]]|$1|13|3|-4|5|6|7|28|8|@]|D|@]|E|$]]]|14|$15|$5|16|17|18|E|$19|1A]]]]

You can follow these instruction if you want to have some structure in your <code>~/.kube</code> directory.
<ol>
<li>Add the following snippet to your <code>~/.bashrc</code></li>
<li>Add config files under <code>~/.kube/config.d</code> separately.</li>
<li>call <code>update_kubeconfigs</code>, or open new terminal</li>
</ol>
<code>update_kubeconfigs</code> just looks at <code>~/.kube/config.d</code> directory and if there were any files newer than the current config file under <code>~/.kube/config</code>, it updates it.
<pre class="lang-sh prettyprint-override"><code>function update_kubeconfigs() {
 [ ! -d &quot;$HOME/.kube/config.d&quot; ] &amp;&amp; mkdir $HOME/.kube/config.d -p -v
 # Will run only if there are new files in the config directory
 local new_files=$(find $HOME/.kube/config.d/ -newer $HOME/.kube/config -type f | wc -l)
 if [[ $new_files -ne &quot;0&quot; ]]; then
 local current_context=$(kubectl config current-context) # Save last context
 local kubeconfigfile=&quot;$HOME/.kube/config&quot; # New config file
 cp -a $kubeconfigfile &quot;${kubeconfigfile}_$(date +&quot;%Y%m%d%H%M%S&quot;)&quot; # Backup
 local kubeconfig_files=&quot;$kubeconfigfile:$(ls $HOME/.kube/config.d/* | tr '\n' ':')&quot;
 KUBECONFIG=$kubeconfig_files kubectl config view --merge --flatten &gt; &quot;$HOME/.kube/tmp&quot;
 mv &quot;$HOME/.kube/tmp&quot; $kubeconfigfile &amp;&amp; chmod 600 $kubeconfigfile
 export KUBECONFIG=$kubeconfigfile
 kubectl config use-context $current_context --namespace=default
 fi
}

# This will call each time you source .bashrc, remove it if you want to call it manually each time
update_kubeconfigs
</code></pre>
Removing files form <code>~/.kube/confing.d</code> will not invoke the script again. Also as @rafaelrezend pointed out, checkout for name conflicts in the config files, that might cause issues.
<a href="https://gist.github.com/rzjfr/f46e25829492cdf6ce9eb3a28a712acc" rel="nofollow noreferrer">Github gist</a>

blocks|key|5712954|text|接下来，我不建议使用kubectl合并kubeconfig文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5712955|5712956|如上所述是手动操作(设置环境变量等)。|unordered-list-item|5712957|的缺点是，当通过"kubectl+config+|5712958|-+context“使用此上下文时，它会将当前上下文写入kubeconfig文件。因此，这会影响使用相同kubeconfig文件中的上下文的其他终端会话(它们突然都指向相同的上下文)。|5712959|5712960|取而代之的是，我建议使用一个工具来规避这样的问题，例如递归地搜索和显示kubeconfig文件的所有可用上下文，并在临时副本上工作。|5712961|查看kubeswitch+(我编写的用于处理>1000kubeconfig文件的工具)和this+section+explaining+how+it+works。|offset|length|5712962|如果你想找一个还能做名称空间切换和其他相关事情的工具，看看"kubie“吧。|5712963|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/danielfoehrKn/kubeswitch|1|https://github.com/danielfoehrKn/kubeswitch#how-it-works^0|0|0|0|0|0|0|0|2|A|0|18|10|1|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|14|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|16|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|18|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|19|8|@]|9|@$O|1A|P|1B|1|1C]|$O|1D|P|1E|1|1F]]|A|$]]|$1|Q|3|R|5|6|7|1G|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]|10|$5|V|W|X|A|$Y|11]]]]

Going forward, I do not recommend merging kubeconfig files using kubectl.
<ul>
<li>it is a manual effort as seen above (set environment variables etc.)</li>
<li>has the disadvantage that when using this context via &quot;kubectl
config use-context&quot; it WRITES the current context to the kubeconfig file. Thus,
this influences other terminal sessions that use a context from the same
kubeconfig file (they all suddenly point to the same context).</li>
</ul>
Instead, I would recommend using a tool that circumvents such issues by e.g recursively search &amp; displays all available contexts for kubeconfig files and works on a temporary copy.
Checkout <a href="https://github.com/danielfoehrKn/kubeswitch" rel="nofollow noreferrer">kubeswitch</a> (the tool I wrote to deal with &gt; 1000 kubeconfig files) and <a href="https://github.com/danielfoehrKn/kubeswitch#how-it-works" rel="nofollow noreferrer">this section explaining how it works</a>.
If you look for a tool that also does namespace switching and other related things, take a look at &quot;kubie&quot;.

blocks|key|4295732|text|正如@talarczykco在顶部答案的评论中所提到的，通过管道返回相同的~/.kube/config只会写入第二个文件，并且您将丢失原始内容！|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4295733|这里有一种更安全的方法，先捕获完整的输出，然后再使用管道。|4295734|注意：必须用"将变量kubeconfig括起来，否则会丢失所有换行符！|BOLD|4295735|konfig=$(KUBECONFIG=~/.kube/config:new-config.yaml+kubectl+config+view+--flatten)

echo+"$konfig"+>+~/.kube/config|code-block|syntax|javascript|4295736|entityMap^0|11|E|0|0|0|3|6|1|A|A|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|V|8|@$9|W|A|X|B|J]|$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|K|3|L|5|M|7|12|8|@]|D|@]|E|$N|O]]|$1|P|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|Q|$]]

As mentioned in the comment by @talarczykco on the top answer, piping back to the same <code>~/.kube/config</code> will only write the second file and you will lose the original content!
Here is a safer way to first capture the full output then pipe.
Note must surround the variable <code>kubeconfig</code> with <code>&quot;</code> otherwise you lose all newlines!
<pre><code>konfig=$(KUBECONFIG=~/.kube/config:new-config.yaml kubectl config view --flatten)

echo &quot;$konfig&quot; &gt; ~/.kube/config
</code></pre>

blocks|key|4295747|text|有可能，请按照以下步骤操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4295748|从您的配置文件创建备份：cp+~/.kube/config-bkp|offset|length|style|CODE|4295749|使用新的配置文件创建一个文件：vi+~/.kube/new-config|4295750|将它们合并到配置文件中：KUBECONFIG=~/.kube/config:~/.kube/new-config+kubectl+config+view+--flatten+>+~/.kube/config|4295751|要查看可用的上下文，请使用：kubectl+config+get-contexts|4295752|要更改上下文，请使用：kubectl+config+use-context+YOUR-CONTEXT-NAME|4295753|entityMap^0|0|C|L|0|F|L|0|C|2J|0|E|R|0|B|18|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|14|8|@$D|15|E|16|F|G]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|Q|$]]

It's possible, follow the steps:
create a backup from your config file:
<code>cp ~/.kube/config-bkp</code>
create a file with your new config file:
<code>vi ~/.kube/new-config</code>
merge them into config:
<code>KUBECONFIG=~/.kube/config:~/.kube/new-config kubectl config view --flatten &gt; ~/.kube/config</code>
To see the available contexts use:
<code>kubectl config get-contexts</code>
To change the context use:
<code>kubectl config use-context YOUR-CONTEXT-NAME</code>

blocks|key|2183466|text|如果你更喜欢命令行工具，我可以强烈推荐:+KubeCM，它也可以合并，切换，添加...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2183467|kubecm+add+-f+./your_new_config|code-block|syntax|javascript|2183468|系统将要求您要么合并到~/.kube/config，要么在当前文件夹中创建一个.yml文件。|offset|length|style|CODE|2183469|https://github.com/sunny0826/kubecm|2183470|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|B|E|0|0|Z|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|W|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|X|8|@$I|Y|J|Z|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|10|8|@]|9|@$I|11|J|12|1|13]]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|N]]]]

If you prefer a CLI tool I can highly recommend: KubeCM, which is also able to merge, switch, add...
<pre><code>kubecm add -f ./your_new_config
</code></pre>
You would be asked either to merge into <code>~/.kube/config</code> or create a .yml file in your current folder.
<a href="https://github.com/sunny0826/kubecm" rel="nofollow noreferrer">https://github.com/sunny0826/kubecm</a>

blocks|key|4295782|text|我将每个集群的yaml文件分开，然后将它们与以下python脚本组合：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4295783|import+argparse
import+yaml
parser+=+argparse.ArgumentParser()
parser.add_argument('files',+metavar='YAMLFILES',+type=argparse.FileType('r'),+nargs='*')
args+=+parser.parse_args()

y+=+{'apiVersion':+'v1',+'kind':+'Config',+'clusters':+[],'contexts':+[],
++++'current-context':+None,+'preferences':+{},+'users':+[]}
for+a+in+args.files:
++++f+=+yaml.load(a,+Loader=yaml.Loader)
++++y['clusters'].append(f['clusters'][0])
++++y['contexts'].append(f['contexts'][0])
++++y['users'].append(f['users'][0])
++++y['current-context']+=+f['contexts'][0]['name']

print(yaml.dump(y,+Dumper=yaml.Dumper))|code-block|syntax|javascript|4295784|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I keep the yaml files for each cluster separate and then combine them with this python script:
<pre class="lang-py prettyprint-override"><code>import argparse
import yaml
parser = argparse.ArgumentParser()
parser.add_argument('files', metavar='YAMLFILES', type=argparse.FileType('r'), nargs='*')
args = parser.parse_args()

y = {'apiVersion': 'v1', 'kind': 'Config', 'clusters': [],'contexts': [],
 'current-context': None, 'preferences': {}, 'users': []}
for a in args.files:
 f = yaml.load(a, Loader=yaml.Loader)
 y['clusters'].append(f['clusters'][0])
 y['contexts'].append(f['contexts'][0])
 y['users'].append(f['users'][0])
 y['current-context'] = f['contexts'][0]['name']

print(yaml.dump(y, Dumper=yaml.Dumper))
</code></pre>

Is there a simple <code>kubectl</code> command to take a <code>kubeconfig</code> file (that contains a cluster+context+user) and merge it into the ~/.kube/config file as an additional context?

How to merge kubectl config file with ~/.kube/config?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

是否有一个简单的kubectl命令可以将kubeconfig文件(包含cluster+context+user)作为附加上下文合并到~/.kube/config文件中？

问如何将kubectl配置文件与~/.kube/config合并？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何将kubectl配置文件与~/.kube/config合并？EN