Error: No service definition found for 'postgres' about cds-pg HOT 6 CLOSED

node ➜ /workspaces/cap-ratings $ ping postgres-svc
PING postgres-svc (172.18.0.2) 56(84) bytes of data.
64 bytes from cap-infra-postgres-svc-1.cap-network (172.18.0.2): icmp_seq=1 ttl=64 time=0.080 ms
64 bytes from cap-infra-postgres-svc-1.cap-network (172.18.0.2): icmp_seq=2 ttl=64 time=0.089 ms
64 bytes from cap-infra-postgres-svc-1.cap-network (172.18.0.2): icmp_seq=3 ttl=64 time=0.089 ms
64 bytes from cap-infra-postgres-svc-1.cap-network (172.18.0.2): icmp_seq=4 ttl=64 time=0.122 ms
64 bytes from cap-infra-postgres-svc-1.cap-network (172.18.0.2): icmp_seq=5 ttl=64 time=0.128 ms
64 bytes from cap-infra-postgres-svc-1.cap-network (172.18.0.2): icmp_seq=6 ttl=64 time=0.164 ms
64 bytes from cap-infra-postgres-svc-1.cap-network (172.18.0.2): icmp_seq=7 ttl=64 time=0.091 ms
64 bytes from cap-infra-postgres-svc-1.cap-network (172.18.0.2): icmp_seq=8 ttl=64 time=0.170 ms
64 bytes from cap-infra-postgres-svc-1.cap-network (172.18.0.2): icmp_seq=9 ttl=64 time=0.191 ms
64 bytes from cap-infra-postgres-svc-1.cap-network (172.18.0.2): icmp_seq=10 ttl=64 time=0.189 ms
64 bytes from cap-infra-postgres-svc-1.cap-network (172.18.0.2): icmp_seq=11 ttl=64 time=0.250 ms
64 bytes from cap-infra-postgres-svc-1.cap-network (172.18.0.2): icmp_seq=12 ttl=64 time=0.259 ms
^C
--- postgres-svc ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 11223ms
rtt min/avg/max/mdev = 0.080/0.151/0.259/0.059 ms
node ➜ /workspaces/cap-ratings $ npm run deploy   

> [email protected] deploy
> npx cds-pg deploy app --to postgres

[cds.connect] - No service definition found for 'postgres', as required by 'cds.requires.postgres': {
  impl: 'cds-pg',
  model: [ 'app' ],
  credentials: {
    host: 'postgres-svc',
    port: '5432',
    user: 'slonik',
    password: 'topsekret',
    database: 'cap-ratings',
    schema: 'public'
  }
}
(node:2384) UnhandledPromiseRejectionWarning: Error: No service definition found for 'postgres'
    at AsyncFunction.connect.to (/workspaces/cap-ratings/node_modules/@sap/cds/lib/connect/index.js:42:11)
    at async Object.to (/workspaces/cap-ratings/node_modules/@sap/cds/lib/deploy.js:21:23)
    at async deploy (/workspaces/cap-ratings/node_modules/cds-pg/bin/cds-pg.js:11:3)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:2384) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:2384) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
node ➜ /workspaces/cap-ratings $

node ➜ /workspaces/cap-ratings $ node test-connection.js 
{ one: 1 }