Unable patch Anchore installation where DNS follows different convention
Summary
The istio configuration below only allows specification of the hostname with "anchore." as a prefix. On SIPR we are not able to create our own DNS entries so our hostnames are appname-clustername-random numbers.AWS-Region.domin. The current configuration doesn't allow us to override the hostname with the patch due to the hard coded anchore / anchore-api
istio:
# Toggle istio integration
enabled: false
ui:
# Toggle vs creation
enabled: true
annotations: {}
labels: {}
gateways:
- istio-system/main
hosts:
- "anchore.{{ .Values.hostname }}"
api:
# Toggle vs creation
enabled: true
annotations: {}
labels: {}
gateways:
- istio-system/main
hosts:
- "anchore-api.{{ .Values.hostname }}"Steps to reproduce
Try and use a hostname that doesn't follow the anchore. naming convention
What is the current behavior?
hosts entry looks like anchore.clustername-123456.region.domain
What is the expected behavior?
Hostname should show anchore-clustername-123456.region.domain
Relevant logs and/or screenshots
No logs
Possible fixes
Update line 18 and 27 to be
#18 - "{{ .Values.hostname }}"
#27 - "{{ .Values.hostname }}"/cc {put CODEOWNERs @githandles here}