- Advanced configuration topics
- Upgrading Ambassador
- Statistics and Monitoring
- Need Help?
Global Configuration: Modules
Modules let you enable and configure special behaviors for Ambassador, in ways that may apply to Ambassador as a whole or which may apply only to some mappings. The actual configuration possible for a given module depends on the module.
A module is added to an existing Kubernetes service, e.g., the Ambassador service. If you expect to make frequent changes to your Ambassador configuration, you may want to put the module on a dummy service. This would allow you to isolate Ambassador configuration changes from your production routing configuration. Here is a sample module configuration of both the
--- apiVersion: v1 kind: Service metadata: name: ambassador annotations: getambassador.io/config: | --- apiVersion: ambassador/v1 kind: Module name: ambassador config: enable_grpc_web: True --- apiVersion: ambassador/v1 kind: Module name: tls config: server: enabled: true secret: ambassador-certs redirect_cleartext_from: 80 spec: type: LoadBalancer externalTrafficPolicy: Local ports: - name: http port: 80 targetPort: 80 - name: https port: 443 targetPort: 443 selector: service: ambassador
ambassador module covers general configuration options for Ambassador as a whole. These configuration options generally pertain to routing, protocol support, and the like. Most of these options are likely of interest to operations.
The 'tls' module covers TLS configuration.
authentication module is now deprecated. Use the AuthService manifest type instead.