You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To me this looks like an upstream Kubernetes bug. This conversation mentions some current problems with merge strategies with respect to some fields including ports: kubernetes-sigs/kustomize#3111
the current consensus is that merging should look for a x-kubernetes-list-map-keys field and use the list to merge if the list exists, then fall back to the singular field x-kubernetes-patch-merge-key and use that. The libraries must respect the intent of the schema.
I think their solution still does not account for the issue at hand though. So in my opinion a hacky way to fix it is desirable.
Line
kubenix/modules/generated/v1.27.nix
Line 5190 in e4d0365
protocol
key be present in all helm generated Pod specifications. For example the following kubenix resource definitionfails with the following error
It should not fail when
protocol
is missing from the ports.There are certainly other similar issues with e.g.
EphemeralContainer
which need to be addressed as well.Workaround
Currently I have just deleted the
"protocol"
fromkubenix/modules/generated/v1.27.nix
Line 5190 in e4d0365
Backstory
I ran into this issue while trying to deploy prometheus as a Helm chart. After a bit of debugging I noticed that the prometheus chart doesn't specify the port protocol: https://github.com/prometheus-community/helm-charts/blob/d628ebad62f119ef2985319a5f7a1dd5bee1863b/charts/prometheus/templates/deploy.yaml#L157
The text was updated successfully, but these errors were encountered: