Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test with Consul Connect + ACL + TLS #6502

Closed
schmichael opened this issue Oct 16, 2019 · 7 comments
Closed

Test with Consul Connect + ACL + TLS #6502

schmichael opened this issue Oct 16, 2019 · 7 comments
Labels
theme/consul/connect Consul Connect integration theme/testing Test related issues

Comments

@schmichael
Copy link
Member

An E2E that mimics production environments as closely as possible would be ideal. This would include:

  • 2 jobs/services
    • stretch goal is having one of them be Connect Native
  • Consul configured with ACLs and mTLS
    • stretch goal Nomad configured with ACLs and mTLS (shouldn't be related but would be nice to implement for completeness)

Test sidecar task overrides and job updates to ensure there aren't any unexpected interactions with Consul token handling.

@tgross
Copy link
Member

tgross commented Nov 15, 2019

Reports of problems with these in #6594, #6711, #6714

@stale
Copy link

stale bot commented Feb 16, 2020

Hey there

Since this issue hasn't had any activity in a while - we're going to automatically close it in 30 days. If you're still seeing this issue with the latest version of Nomad, please respond here and we'll keep this open and take another look at this.

Thanks!

@saez0pub
Copy link

please don't auto close this issue

@schmichael schmichael added the theme/testing Test related issues label Feb 28, 2020
shoenig added a commit that referenced this issue Apr 2, 2020
Fixes #6594 #6711 #6714 #7567

e2e testing is still TBD in #6502

Before, we only passed the Nomad agent's configured Consul HTTP
address onto the `consul connect envoy ...` bootstrap command.
This meant any Consul setup with TLS enabled would not work with
Nomad's Connect integration.

This change now sets CLI args and Environment Variables for
configuring TLS options for communicating with Consul when doing
the envoy bootstrap, as described in
https://www.consul.io/docs/commands/connect/envoy.html#usage
@stale
Copy link

stale bot commented May 29, 2020

Hey there

Since this issue hasn't had any activity in a while - we're going to automatically close it in 30 days. If you're still seeing this issue with the latest version of Nomad, please respond here and we'll keep this open and take another look at this.

Thanks!

@spuder
Copy link
Contributor

spuder commented May 29, 2020

No close

@tgross tgross added this to Needs Roadmapping in Nomad - Community Issues Triage Feb 12, 2021
@tgross tgross removed this from Needs Roadmapping in Nomad - Community Issues Triage Mar 3, 2021
@tgross
Copy link
Member

tgross commented Jul 28, 2022

We've had this done for quite a while now and never closed this out. It's running E2E on nightly.

@tgross tgross closed this as completed Jul 28, 2022
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
theme/consul/connect Consul Connect integration theme/testing Test related issues
Projects
None yet
Development

No branches or pull requests

4 participants