Skip to content

Conversation

@ondbeh
Copy link
Contributor

@ondbeh ondbeh commented Jan 16, 2026

The STACKIT SA Token authentication option has been deprecated, direct SA authentication should be the primary auth option going forward.

@ondbeh ondbeh requested a review from fsandel as a code owner January 16, 2026 11:30
@ondbeh ondbeh changed the title docu: update README to remove mentions of token authentication options due to its deprecation. docs: update README to remove mentions of token authentication options due to its deprecation. Jan 16, 2026
@ondbeh ondbeh requested a review from slm0n87 January 19, 2026 08:35
--namespace=default \
--from-literal=auth-token=<STACKIT AUTH TOKEN>
```
For diverse project architectures where zones are spread across varying projects, use an Issuer (namespaces are separate):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To manage the same zone from multiple stackit projects we advised using multiple tokens per project and have one k8s namespace per token.
Now we advise to use an issuer per namespace - but the info to require multiple SA-key's for that is missing.
In the meantime you can also give SA permissions on folder or org level - we could also point that out here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added more information about this into the README. Can you check please?

And mention using a 'master' SA account and attached security concerns
@ondbeh ondbeh requested a review from slm0n87 January 19, 2026 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants