Installing and running APISIX in your infrastructure: Kubernetes with Helm and the Ingress Controller, Gateway API, Docker and Linux packages, etcd, standalone mode, configuration as code and day-two operations.
Using the APISIX Ingress Controller 2.x as a Gateway API implementation: GatewayClass and Gateway setup through GatewayProxy, HTTPRoute mapping to APISIX routes and plugins, and running Gateway API beside existing Ingress resources.
Installing APISIX with the official Helm chart: gateway, etcd and Ingress Controller components, admin key and secrets handling, exposing the data plane, scaling replicas and upgrading chart and image versions.
Removing etcd from Kubernetes deployments with the Ingress Controller 2.x and API-driven standalone mode: APISIX 3.13 requirement, in-memory configuration, full-sync behavior and what you lose compared with etcd.
When to use APISIX CRDs instead of Ingress or Gateway API: ApisixRoute for plugin-rich routes, ApisixConsumer for credentials, ApisixGlobalRule replacing ApisixClusterConfig, and the controller overwriting manual Admin API changes.
Moving from the Docker Compose evaluation setup to production containers: external etcd or standalone config, admin key through the process environment, port exposure, config reload behavior and image upgrades.
Running APISIX on virtual machines with system packages: supported distributions, systemd and environment variables for the admin key, etcd installation, firewalling the admin and control ports, and patching.
Running etcd for APISIX in traditional or decoupled mode: cluster sizing and placement, mTLS, why gRPC to etcd was removed in 3.6, what happens to gateways when etcd is unavailable, backups and upgrades.
Configuring APISIX from a YAML or JSON file with no etcd: the data_plane role, the #END marker, one-second reload checks, secrets and session settings that etcd used to generate, and GitOps delivery of the file.
Keeping routes, services, consumers and plugins in Git and syncing them with ADC: dump, diff, lint and sync in CI, environment promotion, drift detection and the default-value issue that triggers full updates.
Generating gateway routes from OpenAPI 3 documents with ADC convert openapi: what maps automatically, adding plugins and upstreams afterwards, validating requests with the same spec and keeping both in sync.
Using the Control API for health and status: upstream health at /v1/healthcheck, the JSON array change in 3.19, keeping port 9092 private, readiness checks for load balancers and Kubernetes probes.
Running APISIX with no internet access: mirroring packages, images and Helm charts, an internal etcd, plugins that call external services, OpenID Connect discovery inside the enclave and offline upgrade procedures.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.