Allow url modification for all applications

As an engineer I would like the ability to modify the full URL including the last subdomain.

For example for the elasticsearch-kibana instance I would like the ability to modify kibana in kibana.some.host.com

added 1 deleted label

removed 1 deleted label

added bigbang statusdoing labels

So this has been an issue we've known but been too busy (lazy) to address, thank you for suggesting it!

I think the best approach for this is two part:

• leveraging the upstream standards for specifying ingress fqdn's
• templating hostname with package specific overrides at the bigbang level

what this could look like at the package level chart is:

# standard ingress values
ingress:
  enabled: false
  annotations: {}
  labels: {}
  hosts:
    - my.fqdn.com
    - another.subdomain.example.com
  ...

translated to istio simply replaces ingress with istio.

then at the bigbang level, since we're really just an opinionated way of installing multiple charts, we would default to our opinion, but allow the user to override it:

hostname: bigbang.dev

logging:
  values:
    kibana:
      istio:
        hosts:
          - kibana.{{ tpl .Values.hostname . }}

In the (albeit rare) cases when a user wants to override our opinions, they are more than welcome to override the our HelmRelease values with their downstream patch.

Ultimately I think this better encourages good chart design on our part, keeps a simple solution for the 80%, and allows an "comfortably in line with upstream standards" for the 20%

This looks good. I'll update the underlying packages to match this format.

This has me thinking about https://repo1.dso.mil/platform-one/big-bang/umbrella/-/merge_requests/193.

We should move the added specs to:

ingress:
  cert:
    key:
    cert:

that would be inherited globally by default. As @cmcgrath brought up in mattermost, there may be a scenario where we need a different certs for different ingresses and this would allow for that flexibilty long term.

We also need to update the gateways with all these fqdn so the Gateway (default one below) has the FQDNs. So if someone overrides an internal package to change the FQDN there, we need to also expose the ability to add extra hosts in this gateway via the istio operator

spec:
  selector:
    istio: ingressgateway
  servers:
  - hosts:
    - '*'
    port:
      name: http
      number: 80
      protocol: HTTP
    tls:
      httpsRedirect: true
  - hosts:
    - '*.bigbang.dev'
    port:
      name: https
      number: 443
      protocol: HTTPS
    tls:
      credentialName: wildcard-cert
      mode: SIMPLE

assigned to @zdzielinski

mentioned in merge request !216 (closed)

changed milestone to %1.2.0

changed iteration to Big Bang Iterations Feb 23, 2021 - Mar 8, 2021

removed iteration Big Bang Iterations Feb 23, 2021 - Mar 8, 2021

changed milestone to %1.3.0

changed milestone to %1.2.0

changed milestone to %1.3.0

changed milestone to %1.2.0

changed milestone to %1.3.0

changed iteration to Big Bang Iterations Mar 9, 2021 - Mar 15, 2021

unassigned @zdzielinski

This is complete all bigbang applications are working with url modifications. This was tested in the 1.7.0 release on the dogfood cluster deploying with *.dogfood.bigbang.dev.

closed

mentioned in merge request !773 (merged)

removed statusdoing label

mentioned in merge request !3891 (merged)

mentioned in commit 89fbf50f

mentioned in merge request big-bang/product/packages/metrics-server!65 (merged)