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
{{ message }}
Repository navigation
Commit a3fe434
Browse filesBrowse the repository at this point in the historyBrowse files
fix(deploy): hand the process CODEFLY_GRPC_PORT in the deployment (#124)
A deployed FastAPI service with grpc-server on got the gRPC containerPort
and Service port from the kustomize template, but its container env carried
only CODEFLY_CONNECT_PORT. Locally the runtime hands the process
CODEFLY_GRPC_PORT; in the cluster the app had to guess the port the agent
had already rendered into the Service. The scaffold guessed 9090, and a
service that reads the variable strictly crashlooped with KeyError.
The deployment template now projects CODEFLY_GRPC_PORT from
Parameters.GRPCPort whenever GRPCEnabled is set, mirroring the Connect
block, so the variable and the Service port come from the same value. The
Parameters doc comment and the scaffold's main.py comment say so.
TestDeploymentRendersGRPCPort asserts the variable and its value on a
gRPC-enabled render and its absence when gRPC is off; it fails against the
previous template.
Co-authored-by: antoinetoussaint-byte <312536060+antoinetoussaint-byte@users.noreply.github.com>
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
0 commit comments