sorry, cross-posting from #C01P3B761A6 because i realized that channel doesn't get much action these days. i'm sure this has been asked before, but i can't find a firm answer. I see docs that say flyte domains are fixed and unique at a global level, but that doesn't exactly clarify if your flyte control plane can redefine or add new domains. it looks like flyte-core has a config block that allows you to create custom domains:

# -- Domains configuration for Flyte projects. This enables the specified number of domains across all projects in Flyte.
  domain:
    domains:
      - id: development
        name: development
      - id: staging
        name: staging
      - id: production
        name: production

am i reading that config correctly? is there a way to do that using flyte-binary? anyone ever look to see how much work would be required to extend the chart to support the config?

You can add new domains

You can add new domains

is that true for

flyte-binary

as well? i don't see where that is consumed in the configmap. (appologies for the basic question. i took a long break and i'm just getting back into the code)

True for both

@proud-answer-87162 I would avoid Flyte Binary if you want to get very custom with your Flyte deployment. I noticed pretty quickly that most of the documentation is geared around Flyte-Core. Although Flyte core can seem intimidating when you start, if you plan on customizing your deployment, then you'll end up saving a lot of time going the flyte-core path because you'll have better documentation, better support from the community (Flyte-core is the more production-grade version), and something like what you're trying to do is as simple as adding the following to your values.yaml file

configmap:
  domain:
    domains:
      - id: development
        name: development
      - id: staging
        name: staging
      - id: production
        name: production
      - id: some_new_domain
      - name: some_new_domain

@proud-answer-87162 you can set domains in flyte-binary:

configuration:
  inline:
    domain:
      domains:
        - id: domain1
          name: domain1
        - id: domain2
          name: domain2
        - id: domain3
          name: domain3

i need to dig back in and remember how this stuff gets resolved. thanks for the detailed response!

it lands in the configmap https://github.com/flyteorg/flyte/blob/cc49102e4cf2319f0fa0d92d9e689725142086d3/charts/flyte-binary/templates/configmap.yaml#L208-L210