strange signs in consul backend

[scher200]

Dear support,

I found the characters in consul backend a bit strange. My question is, could we make gloo-connect commands work in conjunction with the consul backend? So that changes can be applied in both.

Anyway I would like to compliment your work, it was really what I was lookikng for.

[ilackarms]

thanks for the feedback. the strange symbols you see are actually the result of Gloo leveraging consul's key-value store to store serialized proto messages (which are binary encoded). future versions of gloo may instead serialize to json or yaml to make configuration human readable directly out of consul.

today you can use glooctl to read those objects in yaml form.

can you be more explicit about what you mean by make gloo-connect commands work in conjunction with the consul backend?

[scher200]

Yes, I meant exactly what you described:

future versions of gloo may instead serialize to json or yaml to make configuration human readable directly out of consul.

awesome!

[ilackarms]

i'm still not clear on the meaning of

make gloo-connect commands work in conjunction with the consul backend

can you give an example of a command and what you'd expect it to do?

[scher200]

no all is fine now, thank you!

I am actually trying to deploy it all on kubernetes, but can not find a tutorial. Can you maybe push me in the right direction?