invalid type for io.k8s.api.core.v1.ConfigMap.data: got "map", expected "string"

[priyanko83]

I am running deployAll.ps1 with the required parameters.
All helm infrastructure and charts are installing fine except Gateway Charts: apigwws & apigwms where I am getting below error logs.

Could you kindly investigate what's wrong and update the fixed files? I am very much interested in this sample application and would really like to get it running in my dev cluster.

Thanks in advance for your support!

Installing Api Gateway Chart: apigwms

Helm Command: helm install eshop-apigwms -f app.yaml -f inf.yaml -f ingress_values.yaml --set app.name=eshop --set inf.k8s.dns=eshop.2d318db21eda4f209268.centralus.aksapp.io --set image.pullPolicy=Always --set inf.mesh.enabled=False --set ingress.hosts={eshop.2d318db21eda4f209268.centralus.aksapp.io} --set inf.tls.enabled=False apigwms
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: [ValidationError(ConfigMap.data.admin): invalid type for io.k8s.api.core.v1.ConfigMap.data: got "map", expected "string", ValidationError(ConfigMap.data.static_resources): invalid type for io.k8s.api.core.v1.ConfigMap.data: got "map", expected "string"]

Installing Api Gateway Chart: apigwws

Helm Command: helm install eshop-apigwws -f app.yaml -f inf.yaml -f ingress_values.yaml --set app.name=eshop --set inf.k8s.dns=eshop.2d318db21eda4f209268.centralus.aksapp.io --set image.pullPolicy=Always --set inf.mesh.enabled=False --set ingress.hosts={eshop.2d318db21eda4f209268.centralus.aksapp.io} --set inf.tls.enabled=False apigwws
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: [ValidationError(ConfigMap.data.admin): invalid type for io.k8s.api.core.v1.ConfigMap.data: got "map", expected "string", ValidationError(ConfigMap.data.static_resources): invalid type for io.k8s.api.core.v1.ConfigMap.data: got "map", expected "string"]

[priyanko83]

@mvelosop @erikpique -

I am really looking forward to this excellent sample app you guys have built as a starting point for coming up with AKS based deployment/devops model to propose to my clients.

Hence, it would be very helpful for me if you could help me out with the issue I'm facing.

Many thanks in advance for your help on this.

[hpr112]

I get the same error when trying to deploy with azure devops release, but it works fine when deploying with deploy-all.ps1...

[olaplassen]

I am experiencing the same error when using Azure Devops release pipeline.

[priyanko83]

I am getting it even when I run using deploy-all.ps1
All helm infrastructure and charts are installing fine except the two charts mentioned in issue description

[bjorntli]

Pls send halp.

[hpr112]

Seems to be an error with the syntax in envoy.yaml and the understanding of indent. The fix for me was to mark all the code in envoy.yaml files and add one indent.

[priyanko83]

@hpr112 @mvelosop - Isn't this a pain to manually do such indentation and figure out what's wrong? Are you aware of any IDE/Tooling that can autodetect/show intellisense such that we dont have to spend hours in idnetifying/correcting indentation manually?

I find it immensely painful to create those long running deployment.yaml files, use if/else/loops to replace values from values.yaml files

[sughosneo]

Hi @priyanko83, you could use some tool like Yamllint to validate and format your YAML(s).

Also, just to let you know we have recently updated our scripts to support latest version of K8s in both local and aks related deployment. If you want you could give it a try and see if that's helpful.

Here are the links for the wiki pages.

Local K8s
AKS

Thank you.

[sughosneo]

Hi @priyanko83 , I am closing this issue as of now. If you face any challenges please feel free to write back and reopen it.

Thank you.

[mgsf]

@sughosneo I tried deploying to AKS (.\deploy-all-mac.ps1) and still get the above error. Tried to validate the envoy.yaml at Yamllint as mentioned above and it is shown as Valid. Then indented as suggested by @hpr112 but still this error occurs. Some help in this regard is highly appreciated.

[mgsf]

I have written how to overcome this issue. Try the link and get the deployment done

[sughosneo]

I have written how to overcome this issue. Try the link and get the deployment done

Hi @mgsf , thank you for the update and feedback. I will test out the AKS deployment scenario again from the macOS environment to see if there is any further issue envoy.yaml. Will update this issue accordingly.

[Rosenberg96]

I am experiencing this exact issue on Mac with a local Kubernetes Cluster. The steps outline by @mgsf did unfortunately not resolve my issues.