https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
c
that’s…. super weird.
Let me regroup on DM, I’d like to look at your state file if possible.
g
If I run the 
helm template ...
command suggested in istio install docs, in the generated YAML I can see 3 definitions that seems to be overlapping:
Copy code
apiVersion: "<http://config.istio.io/v1alpha2|config.istio.io/v1alpha2>"
kind: prometheus
metadata:
  name: handler
  namespace: istio-system
Copy code
apiVersion: "<http://config.istio.io/v1alpha2|config.istio.io/v1alpha2>"
kind: stdio
metadata:
  name: handler
  namespace: istio-system
spec:
  outputAsJson: true
c
How strange.
g
Copy code
apiVersion: "<http://config.istio.io/v1alpha2|config.istio.io/v1alpha2>"
kind: kubernetesenv
metadata:
  name: handler
  namespace: istio-system
spec:
can this be a cause?
c
yes, that is the cause.
@gray-city-50684 what version of istio is this?
i
strange i ran the against the exact same helm chart on friday and it seemed to work
c
@incalculable-angle-91273 after looking at your state, it seems like this actually is the problem — there are no existing resources to collide with.
g
1.0.3
Just followed the doc here:
… and then the “Helm install with Helm template” here:
c
yeah, makes sense
I’m actively working on this, I don’t think they’ve actually published the 1.0.3 chart yet.
g
the script that installs the sources installs that
it calls to this other script for version:
it returns 1.0.3
c
I mean they haven't put the version into the helm repo
g
The docs I linked are prelim for 1.1.0, that is what I found first with Google 🙂
c
You can install it manually of course
g
o, I have no idea about that
c
I mean that you are installing manually
g
Helm install command:
helm install install/kubernetes/helm/istio --name istio --namespace istio-system
so it works from whatever the 
<https://git.io/getLatestIstio>
downloads, doesn’t use the central chart repo
(if I read this correctly)
c
That's right.
g
just to make sure I didn’t derail your original thought process: if apiVersion + metadata/name is same (but kind is different) that can cause the unique name error?
c
No.
g
because the “kind” part is different for the 3 I listed, I just realized it (apiVersion, name, namespace is same)
c
I thought you were saying there's duplicates of each
If not then something weird is happening
g
uhh, that’s what I feared - I’m going to shut up now… Sorry
c
I'll take a look soon, sigh
@incalculable-angle-91273 what version are you on
i
1.0.2
c
Ok. Any other information you can give about how to reproduce
i
😓 actually i can’t reproduce it now. I was hacking away on another branch and when i came back and ran 
npm i
it started behaving nicely
3 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by