Enable samlet to create aws cred secrets in the remote clusters

Open
#12 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, go

Research direction

No files, tests, or entry points are named. Read the repository's existing secret-handling and remote-cluster flows first, then determine how AWS credential secrets should be pushed to target clusters while keeping root service credentials in one cluster and addressing the stated SAML authentication blocker.

Written by the indexing model from the issue text.

Description

We can hugely benefit from enabling samlet ability to push secrets down to target remote clusters.

It will enable us to:

  • Keep sensitive 'root' service credentials(the one with access rights to generate new token) withing a single cluster
  • Solve saml auth blocker with infrastructure SaaS providers like Upbound Cloud
Dominant language
Go
Stars
18
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No 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.

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.