Skip to content

Commit d71a168

Browse files
authored
remove section
1 parent 5a95c34 commit d71a168

File tree

1 file changed

+0
-20
lines changed

1 file changed

+0
-20
lines changed

docs/en/latest/FAQ.md

Lines changed: 0 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -54,23 +54,3 @@ When both filters and a PluginConfig CRD are applied:
5454

5555
* If filters are applied first, PluginConfig overrides any overlapping plugin settings.
5656
* If PluginConfig is applied first, filters merge with PluginConfig settings, and overlapping fields from filters take precedence.
57-
58-
### How does APISIX handle TLS certificates from multiple resources?
59-
60-
APISIX supports TLS configuration via Gateway API, Ingress, and ApisixTls resources. Certificates are identified differently:
61-
62-
* Gateway API and Ingress use the certificate itself as the identifier.
63-
* ApisixTls uses the namespace/name as the identifier.
64-
65-
**Certificate conflicts and merging:**
66-
67-
* Gateway API only: Certificates are merged based on their ID.
68-
* Ingress only: Multiple Ingress resources referencing the same certificate may overwrite each other.
69-
* ApisixTls only: Resources do not conflict.
70-
* Mixed Ingress/Gateway API: Conflicts can occur because both use the certificate as ID.
71-
72-
**Host and certificate matching:**
73-
74-
* For the same SNI, selection depends on the data plane’s matching strategy.
75-
* For different SNIs using the same certificate, Ingress or Gateway API SSL resources may be overwritten by the last applied resource.
76-
* Multiple entries for the same SNI using the same type of resource may overwrite each other depending on creation order.

0 commit comments

Comments
 (0)