- 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
Your ingress must be created in the same namespace where you have installed your validator, participant and utilities app.
All ingress traffic is routed through an included proxy listening on <chart-release-name>-ingress:80.
To setup ingress, two things are required:
Set the host in the values file:
# values.yaml
ingressHosts:
internal: <hostname>
Configure your ingress provider to route traffic to the
<chart-release-name>-ingressservice on port80in the namespace you installed your validator, participant and utilities app.
Example¶
Using the Kubernetes default Ingress provider:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: utilities-ingress
namespace: <chart-release-namespace>
spec:
rules:
- host: <hostname>
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: <chart-release-name>-ingress
port:
number: 80