cool-egg-852
08/14/2019, 4:53 AMwhite-balloon-205
import: <id>
to import the resource, and can make changes (like changing minReplicas
from 2 to 1) after the import succeeds as long as they do not cause the resources to be replaced (which would change the id
).
I believe that meets the needs of this scenario - both for standing up new stacks and for updating them later?cool-egg-852
08/14/2019, 2:27 PMwhite-balloon-205
import
if the resource is going to be replaced (hence changing its id
).cool-egg-852
08/14/2019, 2:45 PMinputs to import do not match the existing resource; importing this resource will fail
white-balloon-205
cool-egg-852
08/14/2019, 3:30 PMimport: ...
so that if a new stack is created, it will import it.stocky-island-3676
10/07/2019, 10:36 AMR
in stack A
. Then you’re creating a new stack B
and want to import R
into that, as well. Right?
If so, then you’re managing the same resource R
in two different stacks. Then a change of R
in one stack, say stack A
, interferes with the same R
in stack B
. Why do you want that?
Wouldn’t be a StackReference
the correct thing you want here? (https://www.pulumi.com/docs/intro/concepts/organizing-stacks-projects/#inter-stack-dependencies)cool-egg-852
10/07/2019, 10:49 AMstack A
which contains the GKE cluster with the istio
addon enabled. In order to make istio highly available, I needed to be able to change the minReplicas
. Because we wanted to do everything in IaC, we had to import the resource. But when we go to create stack B
, we didn’t want to have to manipulate the code again by adding the import
option, and again anytime we add a new stack.
In the end we ended up not using the istio
addon because it’s not ready for production, nor do I feel that it will be anytime soon, even if they make it GA
because Google doesn’t seem to know what they are doing.stocky-island-3676
10/07/2019, 10:59 AM.get()
method on the HPA resource. That way the resource is dynamically referenced (even if it would have worked out with the import:
here, as well, when you simply have a different K8s provider per stack).
Did the minReplicas
value stay with what you’ve set? Or was it maybe automatically set back soon afterwards?