Users can specify whether to create a new namespace with Helm template

Open
#446 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, helm, kubernetes
Domain
devops, infrastructure

Research direction

Start with template/workflows/helm/.github/workflows/azure-kubernetes-service-helm.yml, linked from the issue, and trace how Helm command parameters are supplied in the generated workflow. Define how the new parameter controls namespace creation, then verify the generated command includes or omits the namespace flag as requested.

Written by the indexing model from the issue text.

Description

Is your feature request related to a problem? Please describe.
We're working on integrating Fleet manager with Automated Deployment (#426). The role we are targeting to assign onto the integrating app is Fleet RBAC Writer. However, helm upgrade -i command in the draft generated template always creates a namespace, which can't be achieved by the role we want to assign to Fleet as a namespace is a cluster scoped resource. We do not want to just change the role to Cluster Writer yet. This is because in Fleet Manager we want to differentiate 2 personas: one for cluster admin app that can create cluster scoped objects; another for application team app that can create ns scoped objects like deployments.

Can we propose that we introduce a new parameter that will make --create-namespace- flag in the current helm command run optional? If so we can start working on a PR.

Mention what platform you want to support the new feature
Existing platform.

Describe the solution you'd like
Can we propose that we introduce a new parameter that will make --create-namespace- flag in the current helm command run optional? If so we can start working on a PR.

Describe alternatives you've considered
Using a cluster writer role, but we don't want to assume that the same app will do both application deployment and cluster management tasks.

Dominant language
Go
Stars
644
Forks
74
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/draft

All issues in Azure/draft

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.