We use analytics and cookies to understand site traffic. Information about your use of our site is shared with Google for that purpose. Learn more.
Enabling requests to Knative services when additional authorization policies are enabled
Knative Serving system pods, such as the activator and autoscaler components, require access to your deployed Knative services. If you have configured additional security features, such as Istio’s authorization policy, you must enable access to your Knative service for these system pods.
Before you begin
You must meet the following prerequisites to use Istio AuthorizationPolicy:
Enabling Istio AuthorizationPolicy
For example, the following authorization policy denies all requests to workloads in namespace serving-tests
.
$ cat <<EOF | kubectl apply -f -
apiVersion: security.istio.io/v1beta1
kind: AuthorizationPolicy
metadata:
name: deny-all
namespace: serving-tests
spec:
{}
EOF
In addition to allowing your application path, you’ll need to configure Istio AuthorizationPolicy to allow health checking and metrics collection to your applications from system pods. You can allow access from system pods by paths.
Allowing access from system pods by paths
Knative system pods access your application using the following paths:
/metrics
/healthz
The /metrics
path allows the autoscaler pod to collect metrics.
The /healthz
path allows system pods to probe the service.
You can add the /metrics
and /healthz
paths to the AuthorizationPolicy as shown in the example:
$ cat <<EOF | kubectl apply -f -
apiVersion: security.istio.io/v1beta1
kind: AuthorizationPolicy
metadata:
name: allowlist-by-paths
namespace: serving-tests
spec:
action: ALLOW
rules:
- to:
- operation:
paths:
- /metrics # The path to collect metrics by system pod.
- /healthz # The path to probe by system pod.
EOF
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.