• Airlock Secure Access Hub
  • About this document
  • About Airlock Microgateway
  • Release and support information
  • How to establish security controls
  • System architectures
  • Getting started
  • Requirements and limitations
  • Installation, upgrade and uninstallation
  • Configuration
  • Operation
  • Tooling
  • Troubleshooting and support
    • Configuring Content-Security-Policy headers
    • Record HTTP traffic
    • Inspecting the Microgateway Engine via the Envoy administration interface
    • HTTP protocol selection
    • Inspecting the Envoy configuration
    • List Pods with SidecarGateway selectors
    • Listing the SidecarGateway status
    • Pod is not ready
    • Several SidecarGateway CRs point to the same Pod
    • Troubleshooting Microgateway CNI Helm test
    • Troubleshooting Microgateway Operator Helm test
    • Network routing issues
  • Reference documentation
  1. Troubleshooting and support
  2. Listing the SidecarGateway status

Listing the SidecarGateway status

Observing the status of the Microgateway Custom Resources SidecarGateway helps to identify errors quickly.

The following output shows the status of the SidecarGateway, for example:

 
Terminal box
kubectl get sidecargateways.microgateway.airlock.com

Example output:

 
Terminal box
NAME          STATUS   AGE 
webapp   Active   8m28s
webapp2   Error    8m47s