Feedback for "Account Models With Directories and Subaccounts [Feature Set B]"

[ncktz-cbs]

https://help.sap.com/docs/BTP/df50977d8bfa4c9a8a063ddb37113c43/b5a6b58694784d0c9f4ff85f9b7336dd.html

Best practices for Kyma would be a great addition.
Some ideas:

• what is the impact on the proposed Subaccount structure when using Kyma
  - instead of or
  - in addition to CF
• What is the proposed namespace structure (when to use a new namespace)
• naming conventions
• etc.

[annawenger20]

Hi @ncktz-cbs,
first of all, I apologize for only reacting now. I'll check with dev/pm if we can give some recommendations for Kyma. Thanks a lot for this feedback. Kyma is not yet fully covered in this guide.
Best regards
Anna

[grego952]

Hi all,
I received the following feedback:

Kyma access setup is totally different from sap btp access setup.
For namespaces, you can follow what is being done in the k8s ecosystem: create ns for different teams or based on different scenarios.
The naming convention is again a matter of taste or whatever convention you have followed for your CF org/spaces.

Please let me know if more information is needed.

[ncktz-cbs]

Hi Grzegorz,

as mentioned by you, “Kyma access setup is totally different from sap btp access setup.”
For this reason, best practices for Kyma must be covered in the BTP Best Practices Guide. From my point of view, for many customers K8s is a completely new topic. For this reason, they expect recommendations from SAP for naming conventions, namespaces and how this setup should be done in the most feasible way ensuring sustainable operations for the next years.
Starting with a suboptimal setup due to missing best practices usually leads to significantly increased effort in the upcoming years (or due a costly migration to a new stucture).

Additional questions in this context (in addition to the ones above):

• How to split projects/teams with Kyma?
• When does it make sense to create a new Kyma instance (--> new subaccount)?
• When does it make sense to create new namespaces
• etc.
• Everything while keeping in mind that a new Kyma instance does come with an additional price tag - in contrary to a new CF subaccount.

Thanks a lot
Nico

[grego952]

Hi Nico,
Thanks for your feedback.
Since it's a more complex topic, it will be covered by [REDACTED by org owner].

[ncktz-cbs]

Hi Grzegorz,

Unfortunately, I cannot access your link. Could you please provide updates here?

Thanks a lot
Nico

[grego952]

Hi Nico,
Oh, sorry, my bad. It's Kyma's internal link for the managed offering and critical issues.
Basically, the issue covers what you mentioned here and more (onboarding, security, cluster and namespace structure, etc.)
I'll keep you posted about the progress.

Best regards,
Grzegorz

[NHingerl]

Hi Nico,
thank you for your patience and for your great input! :)

I'm currently consolidating your feedback with our other plans to improve the guide and we'll come back to you with updates once they're available. As Anna mentioned, it's pretty complex and may take a while, but we're on it!

Best regards,
Nina

[ncktz-cbs]

Hi Nina,

Any updates on this topic?

Best regards
Nico

[NHingerl]

Hi Nico - still working on it :)

Best regards,
Nina

[NHingerl]

Hi Nico, thank you for your patience, we're still on it.
It takes longer because just slapping the Kyma information (that you and others requested) onto the existing docs might not be helpful; and a more thorough review is ongoing.

I trust that you know how to get in touch with our support if you need specific answers urgently?

[ncktz-cbs]

Hi Nina,

yes, I also have direct contacts through my work at DSAG.

Thanks a lot
Nico

[NHingerl]

Perfect!
We're still working on the docs and will let you know once there are news :)