knative
/
docs
mirror of https://github.com/knative/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

knative services are private by default (#5511) 

Signed-off-by: Paul S. Schweigert <paul@paulschweigert.com>
Co-authored-by: Paul S. Schweigert <paul@paulschweigert.com>
This commit is contained in:
Knative Prow Robot 2023-03-24 22:18:55 +00:00 committed by GitHub
parent 5991ef0d50
commit 4280065157
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 10 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/serving/services/private-services.md
View File

@ -1,20 +1,17 @@
# Configuring private Services # Configuring private Services
By default, Services deployed through Knative are published to an external IP By default, Services deployed through Knative use the `.svc.cluster.local` domain, meaning
address, making them public Services on a public IP address and with a public URL. they are private and thus do not have a public IP address or a public URL.
Knative provides two ways to enable private services which are only available In order to make Knative Services public (with a public IP address and public URL) by default,
inside the cluster: [configure a domain name](../using-a-custom-domain.md) for the Service.
This can be done for a single Service or for all Services on a cluster.
1. To make all Knative Services private, change the default domain to
`svc.cluster.local` by [editing the `config-domain` ConfigMap](https://github.com/knative/serving/blob/main/config/core/configmaps/domain.yaml). This changes all Services deployed through Knative to only be published to the cluster.
1. To make an individual Service private, the Service or Route can be
labelled with `networking.knative.dev/visibility=cluster-local` so that it is not published to the external gateway.
## Using the cluster-local label ## Making individual services private
To configure a Knative Service so that it is only available on the cluster-local network, and not on the public internet, you can apply the To make an individual Service private, the Service or Route can be labelled with
`networking.knative.dev/visibility=cluster-local` label to a Knative Service, a route or a Kubernetes Service object. `networking.knative.dev/visibility=cluster-local` so that it is not published to the external gateway.
- To label a Knative Service: - To label a Knative Service:

4
docs/serving/using-a-custom-domain.md
View File

@ -1,6 +1,6 @@
# Configuring domain names # Configuring domain names
You can customize the domain of an individual Knative Service, or set a global default domain for all Services created on a cluster. The fully qualified domain name for a route by default is `{route}.{namespace}.example.com`. You can customize the domain of an individual Knative Service, or set a global default domain for all Services created on a cluster. The fully qualified domain name for a route by default is `{route}.{namespace}.svc.cluster.local`.
## Configuring a domain for a single Knative Service ## Configuring a domain for a single Knative Service
@ -18,7 +18,7 @@ You can change the default domain for all Knative Services on a cluster by modif
kubectl edit configmap config-domain -n knative-serving kubectl edit configmap config-domain -n knative-serving
``` ```
1. Edit the file to replace `example.com` with the domain you want to use, then remove the `_example` key and save your changes. In this example, `knative.dev` is configured as the domain for all routes: 1. Edit the file to replace `svc.cluster.local` with the domain you want to use, then remove the `_example` key and save your changes. In this example, `knative.dev` is configured as the domain for all routes:
```yaml ```yaml
apiVersion: v1 apiVersion: v1