Hello Awesome-Docker maintainers - I believe we will start seeing more and more Service Mesh tools being added the next few months. We might consider adding a Service Mesh section to handle this. In the meantime, I have added it to Service Discovery as this is the closest section.
Service Mesh tools aim to handle Service Discovery and a much more manageable abstraction. I would recommend everyone to read - https://istio.io/docs/concepts/what-is-istio/overview.html as this explains in great detail what Service Mesh is and the benefits.
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Yes
RULES (because you probably didn't read the guidelines):
Links will be tested with awesome_bot. Please make sure your URL to be listed is unique (do some search queries), otherwise put a link at the end of README.md file.
FORMAT
Use the following format: [Name](Link) - Description.
[Name] should be the title of the project
(Link) should be pointing to a GitHub repository, not to a website
Description. should end with a full stop/period
For GitHub repositories, add the name of the author with a link to its GitHub account after the description, like By [@author](GitHub account)
ORDER: The entries are in lexical order (English letter order)
LABEL (Optional): Add one of the following icons next to the project name like [Name](Link) :icon: - Description.
💲 indicates if one needs a paying subscription to use the project.
🚧 indicates that the project is a work in progress/beta release.
💀 indicates that the project is obsolete, but still worth mentioning it.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/veggiemonk/awesome-docker/pull/462
**Author:** [@vegasbrianc](https://github.com/vegasbrianc)
**Created:** 10/6/2017
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `master`
---
### 📝 Commits (1)
- [`27230db`](https://github.com/veggiemonk/awesome-docker/commit/27230db96ef879dccc191dfcb11fab6efa927872) Added Service Mesh tool @IstioMesh
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
Hello Awesome-Docker maintainers - I believe we will start seeing more and more Service Mesh tools being added the next few months. We might consider adding a Service Mesh section to handle this. In the meantime, I have added it to Service Discovery as this is the closest section.
URL: https://github.com/istio/istio
Service Mesh tools aim to handle Service Discovery and a much more manageable abstraction. I would recommend everyone to read - https://istio.io/docs/concepts/what-is-istio/overview.html as this explains in great detail what Service Mesh is and the benefits.
# By submitting this pull request I confirm I've read and complied with the below requirements.
**Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.**
Yes
- I have read and understood the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/CONTRIBUTING.md)
Yes
- The project submitted conforms to the quality standards outlined in the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/CONTRIBUTING.md)
Yes
- Go to the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/CONTRIBUTING.md) and read it again.
**RULES (because you probably didn't read the guidelines):**
Links will be tested with [awesome_bot](https://github.com/dkhamsing/awesome_bot). Please make sure your URL to be listed is unique (do some search queries), otherwise put a link at the end of `README.md` file.
- FORMAT
- Use the following format: `[Name](Link) - Description.`
- `[Name]` should be the title of the project
- `(Link)` should be pointing to a GitHub repository, not to a website
- `Description.` should end with a full stop/period
- For GitHub repositories, add the name of the author with a link to its GitHub account after the description, like `By [@author](GitHub account)`
- ORDER: The entries are in lexical order (English letter order)
- LABEL (Optional): Add one of the following icons next to the project name like ```[Name](Link) :icon: - Description.```
- :heavy_dollar_sign: indicates if one needs a paying subscription to use the project.
- :construction: indicates that the project is a work in progress/beta release.
- :skull: indicates that the project is obsolete, but still worth mentioning it.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/veggiemonk/awesome-docker/pull/462
Author: @vegasbrianc
Created: 10/6/2017
Status: ❌ Closed
Base:
master← Head:master📝 Commits (1)
27230dbAdded Service Mesh tool @IstioMesh📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
Hello Awesome-Docker maintainers - I believe we will start seeing more and more Service Mesh tools being added the next few months. We might consider adding a Service Mesh section to handle this. In the meantime, I have added it to Service Discovery as this is the closest section.
URL: https://github.com/istio/istio
Service Mesh tools aim to handle Service Discovery and a much more manageable abstraction. I would recommend everyone to read - https://istio.io/docs/concepts/what-is-istio/overview.html as this explains in great detail what Service Mesh is and the benefits.
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Yes
Yes
Yes
RULES (because you probably didn't read the guidelines):
Links will be tested with awesome_bot. Please make sure your URL to be listed is unique (do some search queries), otherwise put a link at the end of
README.mdfile.[Name](Link) - Description.[Name]should be the title of the project(Link)should be pointing to a GitHub repository, not to a websiteDescription.should end with a full stop/periodBy [@author](GitHub account)[Name](Link) :icon: - Description.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.