-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[SMI] SMI Conformance Testing Support #106
Comments
Hi @kumarabd, I've had a look at the OSM adapter wrt SMI conformance testing to gain an overview. If I understand correctly, labels and annotations defined here Is it possible to either specify mesh specific deployments, and/or specify pod specific annotations? |
Uhmm if its insisting on pod specific annotations then I'm afraid we don't have that ability at the moment. @leecalcote Can we discuss over it once before we move forward for consul? Thanks for highlighting @mgfeller |
@mgfeller will you make a comment in reference to this issue in https://docs.google.com/document/d/1HL8Sk7NSLLj-9PRqoHYVIGyU6fZxUQFotrxbmfFtjwc/edit#? |
App deployment in consul: https://github.com/layer5io/learn-layer5/blob/master/deploy/k8s-consul.yaml I should most probably look more closely at SMI and how it is supposed to work exactly :-) |
Copied from Slack conversation, omitting mentions. Michael Gfeller Dec 9th at 9:09 PM What should we do?
See also #106 blake 1 day ago Michael Gfeller 1 day ago Nic Jackson 21 hours ago Lee 11 hours ago Michael Gfeller < 1 minute ago |
Consul 1.10 is out (https://www.consul.io/docs/release-notes/1-10-0), now supporting transparent proxies. Once this version is supported in the adapter, we could have a look at this issue again. |
I guess this issue is solved, can this issue be closed? |
Enhancement Description
Verify the SMI-compatibility of Consul against the standard suite of compliance tests.
The text was updated successfully, but these errors were encountered: