Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create separate AKS namespace per product #487

Open
ootneim opened this issue Mar 7, 2024 · 2 comments
Open

Create separate AKS namespace per product #487

ootneim opened this issue Mar 7, 2024 · 2 comments
Labels
area/infrastructure Issue originates as changes to infrastructure

Comments

@ootneim
Copy link
Member

ootneim commented Mar 7, 2024

Create a AKS namespace per product and connect the pods to the product namespace.
Today all (most) pods are runnng in the default namespace,

  • Studio
  • Autorisasjon
  • Filescan
  • Hendelser
  • Varsling
@ootneim ootneim added the area/infrastructure Issue originates as changes to infrastructure label Mar 7, 2024
@bengtfredh
Copy link
Member

Maybe this can be combined with migrate from daemonset to deployment - and follow up with autoscaling

@annerisbakk annerisbakk transferred this issue from Altinn/altinn-platform Apr 11, 2024
@acn-sbuad
Copy link
Contributor

DNS will be changed when we change the namespace, so ingress route will need to be looked at. And access to secrets in the cluster will also need to be reviewed. Consult team Altinn Infrastructure before making these changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infrastructure Issue originates as changes to infrastructure
Projects
None yet
Development

No branches or pull requests

3 participants