April 2018
Intermediate to advanced
468 pages
14h 34m
English
That's right, you guessed it. You delete as usual, but specify the context:
> kubectl --context=federation-cluster delete configmap
There is just one little twist. As of Kubernetes 1.10, when you delete a federated ConfigMap, the individual ConfigMaps that were created automatically in each cluster remain. You must delete them separately in each cluster. That is, if you have three clusters in your federation called cluster-1, cluster-2, and cluster-3, you'll have to run these extra three commands to get rid of the ConfigMap across the federation:
> kubectl --context=cluster-1 delete configmap > kubectl --context=cluster-2 delete configmap > kubectl --context=cluster-3 delete configmap
This will be rectified ...
Read now
Unlock full access