apisix
Overview
- Namespace:
apisix - Purpose: Apache APISIX API Gateway
- Age: ~2 years
- Status: x Scaled to Zero - No pods running
Workloads
Deployments
| Name | Replicas | Status | Age | Purpose |
|---|---|---|---|---|
| apisix | 0/0 | x Scaled to 0 | 2y127d | API Gateway core |
| apisix-dashboard | 0/0 | x Scaled to 0 | 2y127d | Web UI for APISIX management |
| apisix-ingress-controller | 0/0 | x Scaled to 0 | 2y127d | Kubernetes Ingress controller |
Services
| Name | Type | Cluster IP | External IP | Ports | Purpose |
|---|---|---|---|---|---|
| apisix-admin | ClusterIP | 10.29.63.5 | - | 9180 | Admin API |
| apisix-dashboard | ClusterIP | 10.29.192.183 | - | 80 | Dashboard UI |
| apisix-ingress-controller | ClusterIP | 10.29.101.80 | - | 80 | Ingress controller |
Current Status
All APISIX components are scaled to 0 replicas:
- No API Gateway pods running
- No Dashboard pods running
- No Ingress Controller pods running
Management
View resources:
kubectl get all -n apisix
Scale up APISIX (if needed):
# Scale up main gateway
kubectl scale deployment apisix -n apisix --replicas=2
# Scale up dashboard
kubectl scale deployment apisix-dashboard -n apisix --replicas=1
# Scale up ingress controller
kubectl scale deployment apisix-ingress-controller -n apisix --replicas=1
View deployment details:
kubectl describe deployment apisix -n apisix
Check etcd dependency:
# APISIX requires etcd
kubectl get statefulset -n etcd
Dependencies
APISIX requires etcd for configuration storage. Check the etcd namespace status.
Current etcd status: x Also scaled to 0
Configuration
View ConfigMaps:
kubectl get configmaps -n apisix
View Secrets:
kubectl get secrets -n apisix
Recommendations
Decision Required
Since both APISIX and its LoadBalancer are unused:
Option 1: Remove (if not needed)
# Delete deployments
kubectl delete deployment apisix apisix-dashboard apisix-ingress-controller -n apisix
# Delete LoadBalancer to stop costs
kubectl delete service apisix-gateway -n apisix
# Consider deleting namespace if fully decommissioned
kubectl delete namespace apisix
Option 2: Reactivate (if needed)
# First, ensure etcd is running
kubectl scale statefulset apisix-etcd -n etcd --replicas=3
# Then scale up APISIX
kubectl scale deployment apisix -n apisix --replicas=2
kubectl scale deployment apisix-dashboard -n apisix --replicas=1
kubectl scale deployment apisix-ingress-controller -n apisix --replicas=1
Features (when active)
Apache APISIX provides:
- API Gateway: Route, transform, and manage API traffic
- Load Balancing: Distribute traffic across backend services
- Authentication: Various auth methods (JWT, OAuth, API keys)
- Rate Limiting: Control API request rates
- Caching: Cache responses for performance
- Observability: Metrics, logging, tracing