Multiple attempts required to resolve kafka broker internal domain

26 Replies

b4d5b2fe-0269-4ddf-8196-c06381b56b14


a year ago

does this happen every deploy?


ye


a year ago

are you on metal?



a year ago

try off metal



worked, ty


a year ago

no problem, ill try to reproduce


kafka was on us east, my pod was on metal


a year ago

how long ago was the "pod" service created?


(by pod I meant service)

44hr


a year ago

@BillyDotWS - please remove "runtime": "UNSPECIFIED", from your railway.json file


hmm, what should it be? nothing?


I'm using the auto generated one


a year ago

just outright remove it


👍


a year ago

then after that, you can switch back to metal


a year ago

if you also have that line in any other railway.json elsewhere, now is the time to remove that line too



<:kekw:788259314607325204> fun


a year ago

now you can switch back to metal


a year ago

i like the icons btw


very fruity


seems fine ya


a year ago

yep looks like you are not on the correct runtime


Loading...