Owner: Architect:

Francesco Ilario

Story (Required)

As a Primaza Administrator,
I would like to have an argument to configure the namespace in which Primaza's Service account is created when joining a cluster
so that I can tune my installation and create single namespace Primaza environments

Background (Required)

To create a Primaza environment with Control Plane, Service Agent and Application Agent in the same namespace, we need to being able to define in which namespace the Primaza's Service Account needs to be created.

See epic for arch document link.

Glossary

See glossary in architecture document

Out of scope

NA

In Scope

• Primaza's Service Account namespace

Approach(Required)

Add the service-account-namespace argument to primazactl join worker command for the Primaza Service Account's namespace.
When manipulating the manifests to be applied, if the argument has been set, change its namespace to the one provided by the Primaza Administrator.

Check if service-account-namespace already exists or not, else fail

Demo requirements(Required)

NA

Dependencies

NA

Edge Case

NA

BDD Tests

You can find BDD Test specification for this story in the "Testing Instruction" Field Tab or in the GitHub Issue linked to this story.
Click here for all BDD Tests Issues.

Acceptance Criteria

• Development
  primazactl allows to define the Primaza Service Account's namespace by the mean of the primaza-identity-namespace argument
  add a create-namespace flag to create the primaza-identity-namespace defined namespace

• QE
  There are test cases for custom Primaza Service Account's namespace
  cluster join tests will require access changes

• Docs
  There is a paragraph in our docs dedicated to explaining how the primaza-identity-namespace works

INVEST Checklist

Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated

Legend

Unknown
Verified
Unsatisfied