@ancient-wolf-19325, is there any way to remove namespace must contain -development, -production and -staging ?? i want only name like xyz

It seems likely that you can customize the namespace naming pattern in Flyte by changing the namespace mapping template in your configuration. By default, Flyte uses the template {{ project }}-{{ domain }} (e.g., myproject-development), but you can set it to just {{ project }} to get namespaces like xyz instead of xyz-development, xyz-production, etc. This is controlled by the namespace_mapping.template field in your FlyteAdmin or Helm values configuration files, as shown in flyteadmin_config.yaml and the related namespace.go. However, you should be aware that this change will affect how Flyte organizes workflow executions and may impact isolation between environments. The data sources do not mention any restrictions that require the -development, -production, or -staging suffixes, so removing them by customizing the template appears supported. Would you like more detail on how to update your configuration for this? Sources: - flyteadmin_config.yaml - namespace.go 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 yes

To remove the -development, -production, and -staging suffixes from your Flyte namespaces, update the namespace mapping template in your Flyte configuration. By default, Flyte uses {{ project }}-{{ domain }} as the namespace template. You can change this to just {{ project }} so that all executions for a project use a namespace like xyz. For example, in your FlyteAdmin or Helm configuration, set:

configuration:
  inline:
    namespace_mapping:
      template: "{{ project }}"

This will ensure that when you create a project (e.g., xyz), Flyte will use the namespace xyz for all domains, instead of xyz-development, xyz-production, etc. For more details, see the logic in namespace.go and related discussions in issue #1583. Sources: - namespace.go - issue #1583 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325,

configuration:
  inline:
    namespace_mapping:
      template: "{{ project }}"

add this in flyte-admin-base-config ??

Yes, you should add the

namespace_mapping.template

configuration under the appropriate section in your FlyteAdmin config, such as

flyte-admin-base-config

. This will instruct Flyte to use only the project name (e.g., xyz) as the namespace, instead of the default project-domain pattern. See namespace.go for how the template is used. Make sure to restart FlyteAdmin after making this change for it to take effect. Would you like a sample YAML snippet for this config? Sources: - namespace.go 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 under server.yaml

It seems likely that you should not add the namespace mapping under

server.yaml

. Instead, you should add it in a separate section called

namespace_config.yaml

within your FlyteAdmin configmap (e.g.,

flyte-admin-base-config

). The data sources show that

namespace_mapping.template

is configured in its own YAML file or section, not under

server.yaml

(flyte_helm_generated.yaml). For example:

namespace_mapping:
  template: "{{ project }}"

Place this in

namespace_config.yaml

or the corresponding section in your configmap, not inside

server.yaml

. Would you like more detail on how to structure your configmap? Sources: - flyte_helm_generated.yaml 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325, i should add something like this namespace_mapping.yaml

namespace_mapping:
  template: "{{ project }}"

Yes, that's correct. You should create a file like

namespace_mapping.yaml

with the following content:

namespace_mapping:
  template: "{{ project }}"

This will configure Flyte to use only the project name as the namespace. Make sure this file is referenced or merged into your FlyteAdmin configmap so FlyteAdmin loads it, as shown in namespace.go. Sources: - namespace.go 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 helm install failing with below error (combined from similar events): Error creating: pods "datacatalog-bf8484bb4-xzg54" is forbidden: failed quota: project-quota: must specify limits.cpu for: run-migrations; limits.memory for: run-migrations

This error means your Kubernetes cluster enforces a ResourceQuota, and the

datacatalog

pod (specifically the

run-migrations

container) is missing

limits.cpu

and

limits.memory

settings. You need to set both CPU and memory limits for all containers in your Helm values or deployment YAML. See the resource section in datacatalog deployment for the correct place to add these. Would you like a sample values.yaml snippet to resolve this? Sources: - datacatalog deployment 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 yes

Add the following to your

values.yaml

under the

datacatalog

section to ensure both the main and

run-migrations

containers have CPU and memory limits:

datacatalog:
  resources:
    limits:
      cpu: 500m
      memory: 500Mi
    requests:
      cpu: 100m
      memory: 100Mi

This will set the required resource limits and requests for all containers in the datacatalog deployment, satisfying the ResourceQuota. For reference, see the datacatalog deployment template. Sources: - https://github.com/flyteorg/flyte/blob/master/charts/flyte-core/values-keycloak-idp-flyteclients-without-browser.yaml - https://github.com/flyteorg/flyte/pull/3762 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.