Skip to content

etcd_docker 3: Incorporate docker based etcd integration package into… (#4147)#4155

Closed
andrewmains12 wants to merge 1 commit intopr/andrewmains12/amains/grpc-update/etcd_tests.review/7aeae843from
pr/andrewmains12/amains/grpc-update/etcd_tests.review/263fed13
Closed

etcd_docker 3: Incorporate docker based etcd integration package into… (#4147)#4155
andrewmains12 wants to merge 1 commit intopr/andrewmains12/amains/grpc-update/etcd_tests.review/7aeae843from
pr/andrewmains12/amains/grpc-update/etcd_tests.review/263fed13

Conversation

@andrewmains12
Copy link
Copy Markdown
Contributor

PR 3 for #4144

High level approach is as described in #4144 .

This PR incorporates the new test package into our unittests. Usage is via the etcdintegration package, which
makes it transparent to the test code; it simply gets an etcd server started via different means.

One piece of weirdness to call out here: the package currently relies on autosync being disabled on the client side.
This is because the advertise client URL (aka what etcd tells clients to connect to) isn't correct for the open port on the host.

That is we have:

  • etcd: listen on container port 0.0.0.0:2379, advertise 0.0.0.0:2379
  • docker: expose etcd port 2379 to 0.0.0.0:0 on host machine (random free port)
  • client: connect to etcd via host machine.

We could probably make this better.


Stack:

⚠️ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

#4147)

PR 3 for #4144

High level approach is as described in #4144 .

This PR incorporates the new test package into our unittests. Usage is via the `etcdintegration` package, which
makes it transparent to the test code; it simply gets an etcd server started via different means.

One piece of weirdness to call out here: the package currently relies on autosync being *disabled* on the client side.
This is because the advertise client URL (aka what etcd tells clients to connect to) isn't correct for the open port on the host.

That is we have:

- etcd: listen on container port 0.0.0.0:2379, advertise 0.0.0.0:2379
- docker: expose etcd port 2379 to 0.0.0.0:0 on host machine (random free port)
- client: connect to etcd via host machine.

We could probably make this better.

commit-id:263fed13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant