Adnan Abdulhussein
Adnan Abdulhussein
it won't know, you're right that it'll be faster if upgrading or after deleting. That said, I don't think we'll change this as it's meant to be a cache and...
Thanks for mocking up an example of what this might look like, but I feel like I'm missing some context here. I would love to understand more about the Helm...
Thanks for adding additional context. My main concern here would be to avoid creating a separate API if we can and rather make some changes to make this a better...
> When I access the UI using the node port What node port are you using to access the UI? It should be the node port of your ingress controller....
cc @pierreozoux who was working on a common Ingress template in https://github.com/kubernetes/charts/pull/794
@cch0 does `helm install --name myrelease --dry-run --debug mychart` work for you? Also what version of Helm do you have?
hmm, I'm not sure why .Release would be empty. @bacongobbler have you seen this before?
In https://github.com/prydonius/common-chart/blob/merge-approach/common/templates/_deployment.yaml#L9 I've set the label used in the Deployment PodSpec to just `app` because of this issue - this is what most of the charts in kubernetes/charts follow.
The Deployment uses the labels defined in it's PodSpec as the selector for ReplicaSets by default, and if these change during upgrade it can't refer back to the old ReplicaSet....
> common.Chartref should not contain the version of the chart as it causes upgrades to fail or rather common.Chartref is not suitable to be used as as selector is it...