This repository was archived by the owner on May 5, 2025. It is now read-only.
guides: Creating a PrivateLink to TriggerMesh Services #297
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sameersbn
force-pushed
the
knative-privatelink
branch
from
1181590 to
4747f01
Compare
jmcx
approved these changes
Aug 5, 2022
docs/guides/knative-privatelink.md
Outdated
| [PrivateLink](https://aws.amazon.com/privatelink) is a service that enables you to establish private connectivity | ||
| between VPCs and services hosted on Amazon Web Services (AWS) or on-premises, | ||
| without exposing data to the internet. Let’s look at the configuration required | ||
| to access Knative services deployed on an AWS Elastic Kubernetes Service (AWS) |
There was a problem hiding this comment.
same comment about Knative => TriggerMesh
docs/guides/knative-privatelink.md
Outdated
| @@ -0,0 +1,136 @@ | |||
| # Creating a PrivateLink to Knative Services | |||
There was a problem hiding this comment.
Is there a way we can spin this more around exposing TriggerMesh services than Knative? if it makes sense.
docs/guides/knative-privatelink.md
Outdated
|
|
||
| ## Configuring the Istio Ingress Gateway | ||
|
|
||
| In the default configuration, the Istio networking layer for Knative creates an |
There was a problem hiding this comment.
Maybe worth mention something like
"the Istio networking layer (or other such as Contour or Kourrier)"
jmcx
approved these changes
Aug 5, 2022
|
|
||
| Before we set up the PrivateLink, let’s make sure that the VPC to which our EKS | ||
| cluster is attached has the DNS hostnames feature enabled. This is needed in order | ||
| to be able to access our Knative services using the URL configured for the services. |
There was a problem hiding this comment.
knative still mentioned here, maybe not problem
| ## Configuring the Istio Ingress Gateway | ||
|
|
||
| The Istio networking layer (or others such as Kourier) creates an Elastic Load | ||
| Balancer (ELB) allowing public access to the Knative services running in the cluster. |
There was a problem hiding this comment.
knative still mentioned here, maybe not problem
|
|
||
| To access the TriggerMesh services via the PrivateLink, we can create an EC2 instance, | ||
| in the consumers AWS account, on the same VPC in which the endpoint was created | ||
| and use cURL to reach the Knative service endpoints. |
There was a problem hiding this comment.
knative still mentioned here, maybe not problem
sameersbn
force-pushed
the
knative-privatelink
branch
from
f20b9d4 to
1f5b46f
Compare
sameersbn
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #296