https://pulumi.com logo
Join Slack
Powered by
Deploying this: ``` const k8sDashboardChart = new ...
# general
f
Deploying this:
Copy code
const k8sDashboardChart = new k8s.helm.v2.Chart("k8s-dashboard", {
    repo: "stable",
    chart: "kubernetes-dashboard",
    version: "1.5.2",
    namespace: "kube-system"
}, {providers: {kubernetes: k8sProvider}});
results in
Copy code
error: Plan apply failed: 2 errors occurred:
    	* Timeout occurred for 'k8s-dashboard-kubernetes-dashboard'
    	* Service does not target any Pods. Selected Pods may not be ready, or field '.spec.selector' may not match labels on any Pods
Any idea why this would happen?
i
Are there worker nodes in the cluster?
f
Yes
Copy code
kubectl get nodes
NAME                                         STATUS   ROLES    AGE    VERSION
ip-10-213-18-34.us-west-2.compute.internal   Ready    <none>   123m   v1.12.7
ip-10-213-5-19.us-west-2.compute.internal    Ready    <none>   124m   v1.12.7
I can deploy other pods.
This may have to do with deploying into the kube-system namespace?
This seems to be a problem specific to Pulumi. I can't find any k8s resources on this issue.
I don't think Pulumi is respecting the 
namespace
property set on the 
k8s.helm.v2.Chart
.
h
FWIW I have tried to use the 
namespace
property and it had no effect on which namespace the pods were deployed to
f
I assume that's a bug, right?
h
I’m guessing?
f
Wow, most of the issues in the kubernetes repo have to do with namespaces haha.
c
pulumi is looking at the resources and trying to determine if they’re alive.
it does not look like they’re alive so we error out.
the application step is identical to 
kubectl apply
so there is a really high chance that this app is not healthy.
f
c
yes, but are the pods alive?
f
I deleted that stack. I can try creating it again.
c
if the pods are not alive, then it’s not a pulumi bug
f
I forget exactly what happened. I'll create the stack again.
Open in Slack
PreviousNext
Powered by