elegant-dress-88912
10/22/2019, 2:39 AMdata
section is updated. is it a known issue or expected behavior? Can't find it issues on github.
kubernetes:core:ConfigMap argocd-cm replace [diff: ~data]
creamy-potato-29402
10/22/2019, 5:09 AMdata
as a field that requires replacement, pulumi will orchestrate an operation that creates the new configmap, updates all references to it, and then when those updates succeed, deletes the old configmap.elegant-dress-88912
10/22/2019, 5:41 AMmetadata.name
for the configmap. That's why I expect pulumi to update it in place as kubectl would do.
Pulumi does this (in-place update) then I use ConfigFile
, why it behaves differently in case of ConfigMap
?
Also, it fails during replace, because it tries to create new configmap with the same name before deleting the old one. Actually, replace would even work for me, but this replace failure breaks things completely.creamy-potato-29402
10/22/2019, 5:45 AMConfigFile
, it should definitely replace it it does in any other case. It should also never try to create an object with the same name before deleting the old one. do you have more details on this?elegant-dress-88912
10/22/2019, 5:46 AMcreamy-potato-29402
10/22/2019, 5:46 AMelegant-dress-88912
10/22/2019, 5:47 AMcreamy-potato-29402
10/22/2019, 5:47 AMelegant-dress-88912
10/22/2019, 5:48 AMkubernetes resource 1.2.3 48 MB n/a 3 hours ago
kubernetes resource 1.1.0 53 MB n/a 3 hours ago
creamy-potato-29402
10/22/2019, 5:49 AMelegant-dress-88912
10/22/2019, 5:49 AM"@pulumi/kubernetes": "^1.1.0",
creamy-potato-29402
10/22/2019, 5:49 AMelegant-dress-88912
10/22/2019, 5:50 AMcreamy-potato-29402
10/22/2019, 5:50 AMelegant-dress-88912
10/22/2019, 5:54 AMcreamy-potato-29402
10/22/2019, 5:54 AMelegant-dress-88912
10/22/2019, 5:56 AMcreamy-potato-29402
10/22/2019, 5:57 AM.spec.selector
, the API server will say “you can’t” because it’s immutable.elegant-dress-88912
10/22/2019, 5:58 AMcreamy-potato-29402
10/22/2019, 5:58 AMelegant-dress-88912
10/22/2019, 5:59 AMcreamy-potato-29402
10/22/2019, 5:59 AM