mirror of https://github.com/istio/istio.io.git
update links (#12079)
This commit is contained in:
Ihor Sychevskyi
GitHub
parent
7034b3ed0a
commit
a7297a1006
|
|
@ -794,7 +794,7 @@ This is needed due to current limitations of Envoy, the proxy used by the standa
|
|||
|
||||
In this subsection you deploy an egress gateway with an SNI proxy, in addition to the standard Istio Envoy proxy. You
|
||||
can use any SNI proxy that is capable of routing traffic according to arbitrary, not-preconfigured SNI values; we used
|
||||
[Nginx](http://nginx.org) to achieve this functionality.
|
||||
[Nginx](https://nginx.org) to achieve this functionality.
|
||||
|
||||
1. Create a configuration file for the Nginx SNI proxy. You may want to edit the file to specify additional Nginx
|
||||
settings, if required.
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ The FitStation team at HP strongly believes in the future of Kubernetes, BPF and
|
|||
|
||||
Throughout the development of FitStation’s large scale and progressive cloud platform, Istio, Cilium and Kubernetes technologies have delivered a multitude of opportunities to make our systems more robust and scalable. Istio was a game changer in creating reliable and dynamic network communication.
|
||||
|
||||
[FitStation powered by HP](http://www.fitstation.com) is a technology platform that captures 3D biometric data to design personalized footwear to perfectly fit individual foot size and shape as well as gait profile. It uses 3D scanning, pressure sensing, 3D printing and variable density injection molding to create unique footwear. Footwear brands such as Brooks, Steitz Secura or Superfeet are connecting to FitStation to build their next generation of high performance sports, professional and medical shoes.
|
||||
[FitStation powered by HP](https://www.fitstation.com) is a technology platform that captures 3D biometric data to design personalized footwear to perfectly fit individual foot size and shape as well as gait profile. It uses 3D scanning, pressure sensing, 3D printing and variable density injection molding to create unique footwear. Footwear brands such as Brooks, Steitz Secura or Superfeet are connecting to FitStation to build their next generation of high performance sports, professional and medical shoes.
|
||||
|
||||
FitStation is built on the promise of ultimate security and privacy for users' biometric data. ISTIO is the cornerstone to make that possible for data-at-flight within our cloud. By managing these aspects at the infrastructure level, we focused on solving business problems instead of spending time on individual implementations of secure service communication. Using Istio allowed us to dramatically reduce the complexity of maintaining a multitude of libraries and services to provide secure service communication.
|
||||
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ It sounds complicated, but not everyone needs to interact with those concepts. S
|
|||
|
||||
Another example of composability in the networking space can be found in the [Google Cloud HTTP(S) Load Balancer](https://cloud.google.com/load-balancing/docs/https/) (GCLB). To correctly use an instance of the GCLB, six different infrastructure objects need to be created and configured. This design is the result of our 20 years of experience in operating distributed systems and [there is a reason why each one is separate from the others](https://www.youtube.com/watch?v=J5HJ1y6PeyE). But the steps are simplified when you’re creating an instance via the Google Cloud console. We provide the more common end-user/role-specific configurations, and you can configure less common settings later. Ultimately, the goals of infrastructure APIs are to offer the most flexibility without sacrificing functionality.
|
||||
|
||||
[Knative](http://knative.dev) is a platform for building, running, and operating serverless workloads that provides a great real-world example of role-centric,
|
||||
[Knative](https://knative.dev) is a platform for building, running, and operating serverless workloads that provides a great real-world example of role-centric,
|
||||
higher-level APIs. [Knative Serving](https://knative.dev/docs/serving/), a component of Knative that builds on Kubernetes and Istio to support deploying and
|
||||
serving serverless applications and functions, provides an opinionated workflow for application developers to manage routes and revisions of their services.
|
||||
Thanks to that opinionated approach, Knative Serving exposes a subset of Istio’s networking APIs that are most relevant to application developers via a simplified
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ types of sensitive data they protect appear in the following table:
|
|||
| --- | --- |
|
||||
|[PCI DSS](https://www.pcisecuritystandards.org/pci_security)|payment card data|
|
||||
|[FedRAMP](https://www.fedramp.gov)|federal information, data and metadata|
|
||||
|[HIPAA](http://www.gpo.gov/fdsys/search/pagedetails.action?granuleId=CRPT-104hrpt736&packageId=CRPT-104hrpt736)|personal health data|
|
||||
|[HIPAA](https://www.gpo.gov/fdsys/search/pagedetails.action?granuleId=CRPT-104hrpt736&packageId=CRPT-104hrpt736)|personal health data|
|
||||
|[GDPR](https://gdpr-info.eu)| personal data|
|
||||
|
||||
[PCI DSS](https://www.pcisecuritystandards.org/pci_security), for example, recommends putting cardholder data
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ Both of these exceptions will go away in a future Istio release, when [Mixer V2]
|
|||
|
||||
Next, when testing Istio's data plane performance at scale, it's important to test not only at increasing requests per second, but also against an increasing number of **concurrent** connections. This is because real-world, high-throughput traffic comes from multiple clients. The [provided scripts](https://github.com/istio/tools/tree/3ac7ab40db8a0d595b71f47b8ba246763ecd6213/perf/benchmark#run-performance-tests) allow you to perform the same load test with any number of concurrent connections, at increasing RPS.
|
||||
|
||||
Lastly, our test environment measures requests between two pods, not many. The client pod is [Fortio](http://fortio.org/), which sends traffic to the server pod.
|
||||
Lastly, our test environment measures requests between two pods, not many. The client pod is [Fortio](https://fortio.org/), which sends traffic to the server pod.
|
||||
|
||||
Why test with only two pods? Because scaling up throughput (RPS) and connections (threads) has a greater effect on Envoy's performance than increasing the total size of the service registry — or, the total number of pods and services in the Kubernetes cluster. When the size of the service registry grows, Envoy does have to keep track of more endpoints, and lookup time per request does increase, but by a tiny constant. If you have many services, and this constant becomes a latency concern, Istio provides a [Sidecar resource](/docs/reference/config/networking/sidecar/), which allows you to limit which services each Envoy knows about.
|
||||
|
||||
|
|
|
|||
|
|
@ -28,4 +28,4 @@ Recently, [we were proud to appoint Neeraj Poddar, Co-founder & Chief Architect
|
|||
|
||||
Our community is currently discussing how the Steering Committee, which oversees marketing and community activities, should be governed, to reflect the expanding community and ecosystem. If you have ideas for this new governance, visit the [pull request on GitHub](https://github.com/istio/community/pull/361) where an active discussion is taking place.
|
||||
|
||||
In the last 12 months, Istio has had commits from [more than 100 organizations](https://istio.teststats.cncf.io/d/5/companies-table?var-period_name=Last%20year&var-metric=commits) and currently has [70 maintainers from 14 different companies](http://eng.istio.io/maintainers). This trend is the kind of contributor diversity the project’s founders intended, and nurturing it remains a priority. Google is excited about what the future holds for Istio, and hopes you’ll be a part of it.
|
||||
In the last 12 months, Istio has had commits from [more than 100 organizations](https://istio.teststats.cncf.io/d/5/companies-table?var-period_name=Last%20year&var-metric=commits) and currently has [70 maintainers from 14 different companies](https://eng.istio.io/maintainers). This trend is the kind of contributor diversity the project’s founders intended, and nurturing it remains a priority. Google is excited about what the future holds for Istio, and hopes you’ll be a part of it.
|
||||
|
|
|
|||
|
|
@ -39,4 +39,4 @@ We also want to make it clear that no single vendor, no matter how large their c
|
|||
|
||||
According to our [seat allocation process](https://docs.google.com/spreadsheets/d/1Dt-h9s8G7Wyt4r16ZVqcmdWXDuCaPC0kPS21BuAfCL8/edit#gid=0), this year Google will be allocated 5 seats and IBM/Red Hat will be allocated 3. As the third largest contributor to Istio in the last 12 months, we are pleased to announce that Salesforce has earned a Contribution Seat.
|
||||
|
||||
The first [election for Community Seats](https://github.com/istio/community/tree/master/steering/elections/2020) begins today. Members have two weeks to nominate themselves, and voting will run from 14 to 27 September. You can learn all about the election in the `istio/community` repository on GitHub. We're also hosting a special [community meeting](http://bit.ly/istiocommunitymeet) this Thursday at 10:00 Pacific to discuss the changes and the election process. We'd love to see you there!
|
||||
The first [election for Community Seats](https://github.com/istio/community/tree/master/steering/elections/2020) begins today. Members have two weeks to nominate themselves, and voting will run from 14 to 27 September. You can learn all about the election in the `istio/community` repository on GitHub. We're also hosting a special [community meeting](https://bit.ly/istiocommunitymeet) this Thursday at 10:00 Pacific to discuss the changes and the election process. We'd love to see you there!
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@
|
|||
<link rel="alternate" type="application/rss+xml" title="Istio News" href="/news/feed.xml">
|
||||
<link rel="alternate" type="application/rss+xml" title="Istio Blog and News" href="/feed.xml">
|
||||
|
||||
<!-- Favicons: generated from img/istio-whitelogo-bluebackground-framed.svg by http://cthedot.de/icongen -->
|
||||
<!-- Favicons: generated from img/istio-whitelogo-bluebackground-framed.svg by https://cthedot.de/icongen -->
|
||||
<link rel="shortcut icon" href="/favicons/favicon.ico" >
|
||||
<link rel="apple-touch-icon" href="/favicons/apple-touch-icon-180x180.png" sizes="180x180">
|
||||
<link rel="icon" type="image/png" href="/favicons/favicon-16x16.png" sizes="16x16">
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ import (
|
|||
"istio.io/istio/pkg/test/scopes"
|
||||
)
|
||||
|
||||
// Builder builds a test of a documented workflow from http://istio.io.
|
||||
// Builder builds a test of a documented workflow from https://istio.io.
|
||||
type Builder struct {
|
||||
steps []Step
|
||||
cleanupSteps []Step
|
||||
|
|
|
|||
Loading…
Reference in New Issue