full-eve-5253609/07/2023, 3:52 PM
mechanism? We sometimes have resource creation fail due to environmental issues. This is usually resolved when re-running
, but we would rather just retry a single resource operation, rather than the whole stack.
stocky-restaurant-9800409/07/2023, 5:18 PM
full-eve-5253609/07/2023, 5:19 PM
resource of the kubernetes provider sometimes fails because the CRDs are not ready yet on the cluster, so ideally we would just have that
resource try to install the helm chart again.
dry-keyboard-9479509/07/2023, 5:23 PM
stocky-restaurant-9800409/07/2023, 8:37 PM
? I know that some resource in that provider does have a
full-eve-5253609/07/2023, 8:42 PM
In this scenario, are there other resources in your stack would be retried that should not be? I'm asking b/c nothing that succeeded should be retried in a normal Pulumi program. Trying to figure out if there's a potential bug.No everything else seems to be working as expected. I think this "retry" feature may also be handy with other resources, too. For example,
may be running a curl command that fails because of an intermittent network issue. In that case, it would be nice to tell Pulumi to only retry that resource so I don't have to run the entire stack deployment.
stocky-restaurant-9800409/07/2023, 8:43 PM
, which is how I solved for stuff not being ready in another codebase. I wouldn't call it ironclad, but it worked pretty reliably. Then you can make your Helm chart resource depend on the command.
full-eve-5253609/07/2023, 8:49 PM
BTW, you can useThat would normally work if I was installing CRDs independently from my Helm chart, but I would like theto run
command.local, which is how I solved for stuff not being ready in another codebase. I wouldn't call it ironclad, but it worked pretty reliably. Then you can make your Helm chart resource depend on the command.
resource to install the required CRDs for that chart.
dry-keyboard-9479509/07/2023, 8:53 PM
full-eve-5253609/07/2023, 8:54 PM
wouldn't have any CRDs, but you get the idea. I have several other 3rd party charts that I am trying to install via the
resource which have CRDs
dry-keyboard-9479509/07/2023, 9:09 PM
, which is how we deploy cert-manager internally
full-eve-5253609/07/2023, 9:12 PM
dry-keyboard-9479509/07/2023, 9:13 PM
echoing-dinner-1953109/08/2023, 7:56 AM
again) but feel free to vote and comment on that.