This is an automated email from the ASF dual-hosted git repository.
navendu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-ingress-controller.git
The following commit(s) were added to refs/heads/master by this push:
new 5beb519f docs: small adjustments to Check CRD status tutorial (#1670)
5beb519f is described below
commit 5beb519f24b0a8dc534e97285bb442721eeb13a4
Author: German Lashevich <[email protected]>
AuthorDate: Thu Feb 16 14:40:27 2023 +0100
docs: small adjustments to Check CRD status tutorial (#1670)
---
docs/en/latest/tutorials/check-crd-status.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/en/latest/tutorials/check-crd-status.md
b/docs/en/latest/tutorials/check-crd-status.md
index cbe8cea7..592cab43 100644
--- a/docs/en/latest/tutorials/check-crd-status.md
+++ b/docs/en/latest/tutorials/check-crd-status.md
@@ -29,13 +29,13 @@ description: A guide to check the synchronization status of
APISIX CRDs.
APISIX CRDs are applied to a Kubernetes cluster using the `kubectl apply`
command. Behind the scenes, Kubernetes verifies the configuration using the
[Open API V3 schema](https://swagger.io/specification/) and its validation
webhooks (if any).
-But this does not mean that the configuration is synchronized and validated by
APISIX. APISIX will convert the declared configuration to APISIX specific
resources and verify it. If the verification fails, the Ingress controller will
log an error message and will retry until the desired state is successfully
synchronized to APISIX.
+But this does not mean that the configuration is synchronized and validated by
APISIX. APISIX will convert the declared configuration to APISIX-specific
resources and verify it. If the verification fails, the Ingress controller will
log an error message and will retry until the desired state is successfully
synchronized to APISIX.
This guide will show how you can check the synchronization status of the CRDs.
## Example with ApisixRoute
-This example uses
[ApisixRoute](https://apisix.apache.org/docs/ingress-controller/references/apisix_route_v2)
resources. But, this applies for other APISIX CRDs like
[ApisixUpstream](https://apisix.apache.org/docs/ingress-controller/references/apisix_upstream),
[ApisixTls](https://apisix.apache.org/docs/ingress-controller/references/apisix_tls_v2),
and
[ApisixClusterConfig](https://apisix.apache.org/docs/ingress-controller/references/apisix_cluster_config_v2).
+This example uses
[ApisixRoute](https://apisix.apache.org/docs/ingress-controller/references/apisix_route_v2)
resources. But this also applies to other APISIX CRDs like
[ApisixUpstream](https://apisix.apache.org/docs/ingress-controller/references/apisix_upstream),
[ApisixTls](https://apisix.apache.org/docs/ingress-controller/references/apisix_tls_v2),
and
[ApisixClusterConfig](https://apisix.apache.org/docs/ingress-controller/references/apisix_cluster_config_v2).
We can deploy a sample ApisixRoute resource:
@@ -56,7 +56,7 @@ spec:
backends:
- serviceName: httpbin-service-e2e-test
servicePort: 80
- EOF
+EOF
```
Once this resource is applied, you can check its synchronization status with
its name as shown below:
@@ -67,7 +67,7 @@ kubectl describe ar httpbin-route
This will give the status as shown below:
-```yaml title="output"
+```text title="output"
...
Status:
Conditions:
