brave-ambulance-98491
03/29/2020, 10:00 PMDeployment
resources show up as "replace" when I update ConfigMap
values. Ideally, these should just "update" in that case. Is this a known issue?better-rainbow-14549
03/30/2020, 8:32 AMbrave-ambulance-98491
03/30/2020, 3:57 PMDeployment
, so I don't love it.gorgeous-egg-16927
03/30/2020, 4:43 PMbrave-ambulance-98491
03/30/2020, 4:44 PMgorgeous-egg-16927
03/30/2020, 4:57 PMbrave-ambulance-98491
03/30/2020, 4:59 PMConfigMap
name, where the Deployment
spec isn't changing at all. Also, did the preview show a replace
or an update
for the Deployment
for you?gorgeous-egg-16927
03/30/2020, 4:59 PMupdate
brave-ambulance-98491
03/30/2020, 5:07 PMorange-policeman-59119
05/20/2020, 1:53 AM# many lines removed
~ spec : {
~ template: {
~ spec : {
~ containers : [
~ [0]: {
~ env : [
# many lines removed
~ [14]: {
~ name : "ENV_VAR_A" => "SOME_NEW_ENV_VAR"
- value : "env-var-a-value"
+ valueFrom: {
+ secretKeyRef: {
+ key : "a-key"
+ name: "on-a-secret-resource"
}
}
}
+ [15]: {
+ name : "ENV_VAR_A"
+ value: "env-var-a-value"
}
Is the reason why because:
• A new env var was introduced into a higher position
• This shifted all the other env vars "down"
• And during that shift, the secretKeyRef was added/removed?
If so I think that's a defect, we already add an annotation to our pod spec with the hash of the secret key data so that when the secret updates, our pods do too~ template: {
metadata: {
annotations: {
checksum/secrets: "[secret]"
}
brave-ambulance-98491
05/20/2020, 4:55 PMConfigMap
(not having Pulumi generate a name for you)? My suspicion was that this was what triggered this bug.