sparse-intern-71089
04/20/2021, 9:51 AMlimited-rainbow-51650
04/20/2021, 11:26 AMlimited-rainbow-51650
04/20/2021, 11:43 AMproud-pizza-80589
04/20/2021, 1:15 PMconst secret = fabricCa.getResource('v1/Secret', 'default', 'ca-tls-cert');
// <https://www.pulumi.com/docs/intro/concepts/resources/#resource-get>
const updatedSecret = k8s.core.v1.Secret.get('tlssecret', secret.id, {
provider,
dependsOn: [fabricCa],
});
export const data = updatedSecret.data.apply((data) => data);
proud-pizza-80589
04/20/2021, 1:15 PMproud-pizza-80589
04/20/2021, 1:16 PMlimited-rainbow-51650
04/20/2021, 1:28 PMlimited-rainbow-51650
04/20/2021, 1:45 PMproud-pizza-80589
04/20/2021, 1:46 PMlimited-rainbow-51650
04/20/2021, 2:05 PMfast-dinner-32080
04/20/2021, 4:55 PMlimited-rainbow-51650
04/20/2021, 6:56 PMService
is created. Why don’t I get this value (which remains unchanged) if I just add e.g. an annotation?gorgeous-egg-16927
04/20/2021, 9:15 PMhealthPortNumber
code is running prior to the nodePort
value resolving (it’s usually set by the cluster). This seems like a possible oversight in the await logic for Service resources.
If you look at https://www.pulumi.com/docs/reference/pkg/kubernetes/core/v1/service/#service you’ll notice that the nodePort
isn’t considered as part of the readiness check.gorgeous-egg-16927
04/20/2021, 9:16 PMlimited-rainbow-51650
04/22/2021, 11:18 AMbillowy-army-68599
limited-rainbow-51650
04/23/2021, 12:21 PM