Skip to content
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

Add CitrixLab PH Case Study to Istio Documentation #16205

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

Conversation

CitrixLab
Copy link

Description

This PR introduces CitrixLab PH as a new case study in the Istio documentation. CitrixLab PH is an innovative digital solutions startup company in the Philippines that is actively contributing to the open-source ecosystem. Their work demonstrates the integration and value of Istio in a modern microservices architecture.

Logo: Added CitrixLab PH's logo to the case study section.
URL: Linked CitrixLab PH’s official site for more details: https://citrixlab.vercel.app/.

We hope this addition can inspire other developers and organizations to consider Istio for managing their microservices in an efficient and scalable way.

Reviewers

  • Ambient
  • [x ] Docs
  • Installation
  • Networking
  • Performance and Scalability
  • Extensions and Telemetry
  • Security
  • Test and Release
  • User Experience
  • Developer Infrastructure
  • Localization/Translation

This PR introduces CitrixLab PH as a new case study in the Istio documentation. CitrixLab PH is an innovative digital solutions startup company in the Philippines that is actively contributing to the open-source ecosystem. Their work demonstrates the integration and value of Istio in a modern microservices architecture.

Logo: Added CitrixLab PH's logo to the case study section.
URL: Linked CitrixLab PH’s official site for more details: https://citrixlab.vercel.app.

We hope this addition can inspire other developers and organizations to consider Istio for managing their microservices in an efficient and scalable way.
Add CitrixLab PH as a Case Study in the Istio Open Source Project
@istio-policy-bot
Copy link

😊 Welcome! This is either your first contribution to the Istio documentation repo, or
it's been a while since you've been here. A few things you should know:

  • You can learn about how we write and maintain documentation, our style guidelines,
    and the available web site features by visiting Contributing to the Docs.

  • In the next few minutes, an automatic preview of your change will be built with
    a full copy of the istio.io website. You can find this preview by clicking on
    the Details link next to the deploy/netlify entry in the status section of this
    page.

  • We care about quality, so we've put in place a number of checks to ensure our documentation
    is top-notch. We do spell checking, sanitize the Markdown, ensure all hyperlinks point to a
    valid location, and more. If your PR doesn't pass one of these checks, you'll see a red X in the
    lint_istio.io entry in the status section. Click on the Details link to get a list of the
    problems with your PR. Fix those problems and push an update; this will automatically re-run the
    tests. Hopefully this time everything will be perfect!

  • Once your changes are accepted and merged into the repository, they will initially show up
    on https://preliminary.istio.io. The changes will be published to https://istio.io
    the next time we do a major release (which typically happens every 3 months or so).
    To publish them sooner, add a cherrypick/release-x.xx label, where x.xx is the current
    release of Istio.

Thanks for contributing!

Courtesy of your friendly welcome wagon.

Copy link

linux-foundation-easycla bot commented Jan 25, 2025

CLA Signed


The committers listed above are authorized under a signed CLA.

@istio-testing istio-testing added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jan 25, 2025
@istio-testing
Copy link
Contributor

Hi @CitrixLab. Thanks for your PR.

I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Copy link
Member

@Arhell Arhell left a comment

Choose a reason for hiding this comment

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

/ok-to-test

@istio-testing istio-testing added ok-to-test Set this label allow normal testing to take place for a PR not submitted by an Istio org member. and removed needs-ok-to-test labels Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/docs ok-to-test Set this label allow normal testing to take place for a PR not submitted by an Istio org member. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants