search

knative-extensions / control-protocol

Control protocol to enable interaction between control plane and data plane without redeploy
Apache License 2.0
2 stars 26 forks source link

Change certificates to include namespace specific SANs #264

Closed davidhadas closed 1 year ago

davidhadas commented 1 year ago

Change certificates to include namespace-specific SANs This applies to all certificates apply from the namespace used by the knative-serving servers and ingress gateways Ensure the same certificate can be used for both clients and servers in support of mTLS

knative-prow[bot] commented 1 year ago

@davidhadas: The label(s) area/networking cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/knative-sandbox/control-protocol/issues/264): >1. Change certificates to include namespace specific SANs >This applies for all certificates apply from the namespace used by the knative-serving servers and ingress gateways > >2. Check if we create ingress a certificate for the ingress namespace and if not create it. > >/area networking Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.