Skip to content

bug(kubernetes): magma secret handling #16

Open
@lucaaamaral

Description

@lucaaamaral

Your Environment

  • Version: 1.8.0
  • Affected Scope: secrets
  • Deployment Environment: kubernetes

Describe the Issue

Josh Lambert complained at slack https://magmacore.slack.com/archives/C0191LLL03S/p1743089892985029

Hey guys! New Magma user here, previous experience with RAEMIS and Open5GS. Having a significantly hard time getting a basic environment working for Orchestrator and NMS in the cloud as unfortunately the documentation has issues and a lot of things don't work as described online. I'm working on a script to automate setup of these requring the user only to do the A-Record and provide an email address. It's on Github here. if anybody with more experience can jump in and help me fix a few rough spots like the secrets management I would appreciate it. This is a work-in-progress but I think once done will make getting people to use Magma much much much easier. I'll actively maintain this and test. Working today on it myself to keep fixing things until it works as a perfect one-shot solution for magma orchestrator/NMS without needing a bunch of Kubernetes or other complex stack knowledge.. 🚀 https://github.com/joshualambert/easy-magma-setup/

To Reproduce

Expected behavior

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here (e.g. logs).

Metadata

Metadata

Labels

bugSomething isn't working

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions