- Overview
- Setup
- Tutorials
- How Tos
- Reference
- DAR Versions
- API Reference
- Commercials API
- Credential API
- Registry API
- Utility.Registry
- Utility.Registry.V0.Configuration.AppReward
- Utility.Registry.V0.Configuration.Instrument
- Utility.Registry.V0.Holding.Allocation
- Utility.Registry.V0.Holding.Burn
- Utility.Registry.V0.Holding.Lock
- Utility.Registry.V0.Holding.Mint
- Utility.Registry.V0.Holding.Transfer
- Utility.Registry.V0.Holding.Unlock
- Utility.Registry.V0.Rule.Transfer
- Utility.Registry.V0.Types
- Utility.Registry.V0.Util
- Utility.Registry.App
- Utility.Holding
- Utility.Registry
- Settlement Utility API
- Collateral Utility API
- Operator Backend API
Ingress¶
Warning
Ingress will undergo a large refactor in the next release of the Utility. Most of this information will change.
All ingress traffic is routed through an included traefik proxy listening on <chart-release-name>-ingress.<chart-namespace>.svc.cluster.local:80
.
To setup ingress, two things are required:
Set the host in the values file:
# values.yaml
ingressHosts:
internal: <hostname>
Configure the ingress provider to route traffic to
<chart-release-name>-ingress.<chart-namespace>.svc.cluster.local:80
Example¶
Using the Kubernetes default Ingress provider:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: utilities-ingress
spec:
rules:
- host: <hostname>
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: <chart-release-name>-ingress.<chart-namespace>.svc.cluster.local
port:
number: 80