Skip to content

Update to APIRule V2 and update packages dependencies. #23961

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

Open
wants to merge 15 commits into
base: master
Choose a base branch
from

Conversation

wuchenjun
Copy link

Changes notes:

  1. Update APIRule to v2.
  2. Update outdated images to latest.
  3. Update packages dependencies.
  4. Update @kubernetes/client-node to 1.3.0.
  5. Enable Istio Sidecar Proxy Injection.

@wuchenjun wuchenjun requested a review from nataliasitko June 6, 2025 08:40
@CLAassistant
Copy link

CLAassistant commented Jun 6, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ wuchenjun
❌ arivnwu
You have signed the CLA already but the status is still pending? Let us recheck it.

@rbrainey
Copy link
Contributor

hi @nataliasitko: would you want to go ahead and review this PR? The license/cla seems to have been compiled with, based on an email conversation with Arvun. I'm only waiting for the review to merge the PR. Thanks,

<!-- border -->![create_ns](create_ns.png)


**3.** Enable Istio Sidecar Proxy Injection

Choose a reason for hiding this comment

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

Screenshot 2025-06-12 at 07 54 22 You can enable sidecar injection during the namespace creation. Maybe it would be easier to include it in the previous step instead of editing the namespace when it's already created

Copy link
Author

Choose a reason for hiding this comment

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

Fixed, move enable sidecar to Create Namespace step


![image-20220214153901104](1645680425240.jpg)
<!-- border -->![api_rule_host](api_rule_host.png)

**2.** Access it in the browser, then the application will return the message that you defined before.

Choose a reason for hiding this comment

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

What message exactly should the application return based on the provided code snippets? Maybe we could also add this information to the tutorial.
I got Hello World, and I thought it was the expected result, but looking at the code snippet, I think I should also see the sub-domain and the zone ID, right?
Screenshot 2025-06-16 at 18 01 35

Copy link
Author

Choose a reason for hiding this comment

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

This tutorial doesn't bind the XSUAA, so cannot see the auth info. User see "Hello World!" is expected result. I will update it into content.

Choose a reason for hiding this comment

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

I think the last tutorial in the mission is the only point where the user can verify whether they have been following the steps correctly or not. I think it might also be helpful if we could add some hints in other tutorials. The only tutorial that comes to my mind, though, is Deploy a Multitenant Application to a Provider subaccount, Kyma Runtime
There, the user could check if the app is deployed correctly by verifying the resources' state, for example, in the Kyma dashboard (or using kubectl)
What do you think? It's just an idea, I don't have any strong opinion about this

Copy link
Author

Choose a reason for hiding this comment

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

Exactly, good idea. I will add the check deployment state in the end of application deployment.

@@ -21,7 +21,7 @@ primary_tag: software-product>sap-business-technology-platform
### Create New Subaccount


Now, a consumer can subscribe to the application through the SAP BTP Account Cockpit.
Now, a consumer can subscribe to the application through SAP BTP cockpit.

Create a new subaccount for the customer in the same Global Account with the multitenant application provider subaccount, for example, called `Customer`.

Choose a reason for hiding this comment

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

In line 29, I would use the heading: Subscribe to Multitenant Application

Copy link
Author

@wuchenjun wuchenjun Jun 17, 2025

Choose a reason for hiding this comment

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

Sure, updated the heading already

@wuchenjun
Copy link
Author

Hi @rbrainey, Fixed all issue from my side. Could you please merge this PR? Thanks a lot!

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.

5 participants