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

Opa blog post #15134

Draft
wants to merge 47 commits into
base: master
Choose a base branch
from
Draft

Opa blog post #15134

wants to merge 47 commits into from

Conversation

antonioberben
Copy link
Member

@antonioberben antonioberben commented May 16, 2024

Description

This PR adds a blog post about how to use OPA with Istio and the benefits of both.

Adding co-author to the loop: @charlieegan3

Reviewers

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

@istio-testing istio-testing added the do-not-merge/work-in-progress Block merging of a PR because it isn't ready yet. label May 16, 2024
@istio-testing
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@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.

@istio-testing istio-testing added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label May 16, 2024
@antonioberben antonioberben marked this pull request as ready for review May 16, 2024 12:44
@antonioberben antonioberben requested a review from a team as a code owner May 16, 2024 12:44
@istio-testing istio-testing removed the do-not-merge/work-in-progress Block merging of a PR because it isn't ready yet. label May 16, 2024
@antonioberben antonioberben marked this pull request as draft May 16, 2024 13:44
@istio-testing istio-testing added the do-not-merge/work-in-progress Block merging of a PR because it isn't ready yet. label May 16, 2024
@istio-testing istio-testing added the needs-rebase Indicates a PR needs to be rebased before being merged label May 17, 2024
@istio-testing istio-testing removed the needs-rebase Indicates a PR needs to be rebased before being merged label May 17, 2024
@antonioberben
Copy link
Member Author

/retest

@antonioberben antonioberben marked this pull request as ready for review May 17, 2024 15:33
@istio-testing istio-testing removed the do-not-merge/work-in-progress Block merging of a PR because it isn't ready yet. label May 17, 2024
@craigbox
Copy link
Contributor

Thanks for the submission, @antonioberben!

Some thoughts before diving into a full edit:

  • For content that is timeless and more "how to do something", you probably want to write it as a documentation guide rather than a blog post. This would make a good integration guide with a blog post to announce the publication of it.
  • I think you need to better level-set as to what a "platform" is: we talk about platform teams and platforms as if we all agree on what they are, which I suspect we do not
  • I feel the "how it works" section needs to come before "try it out", so we know what we're trying
  • you say a cluster with Istio installed is a pre-requisite, and then you tell people how to install Istio with iop.yaml which isn't obviously provided
  • Likewise, opa.yaml needs to be provided. For a blog post or guide, we'd normally expect these files to be inline with an explanation of what they contain

Let me know how you'd like to proceed and I can either help get this into shape for a doc page or a revised blog post.

.spelling Outdated Show resolved Hide resolved
@linsun
Copy link
Member

linsun commented May 30, 2024

Hi @antonioberben Nice blog - does this instruction work with ambient as well?

@antonioberben
Copy link
Member Author

Hi @linsun , it does not work in ambient. I could not make it work with it

@craigbox
Copy link
Contributor

I've suggested to Antonio that we get this one into a Google doc for review there. The current setup won't work as a blog post, because it relies on files that people don't have. We can rework all the content into the doc or the blog as appropriate.

content/en/blog/2024/l7-policy-with-opa/index.md Outdated Show resolved Hide resolved
keywords: [istio,opa,policy,platform,authorization]
---

The era of the platform is here. Behind every great application team, is a great platform, and a great platform _team_. Platforms offer resources and shared functionality to teams so they don't need to build everything from scratch. Platform teams aren’t short of work either, but now is a great time to ask the question: what’s the highest value platform feature you can offer the tenants of your platform?
Copy link
Contributor

Choose a reason for hiding this comment

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

It helps to read posts out loud as you review them. In this one, you say "platform" seven times! I found it a bit hard to parse.

antonioberben and others added 25 commits August 12, 2024 15:26
Co-authored-by: Daniel Hawton <[email protected]>
Co-authored-by: Daniel Hawton <[email protected]>
Co-authored-by: Daniel Hawton <[email protected]>
Co-authored-by: Daniel Hawton <[email protected]>
@antonioberben antonioberben marked this pull request as draft August 12, 2024 13:44
@istio-testing istio-testing added the do-not-merge/work-in-progress Block merging of a PR because it isn't ready yet. label Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/extensions and telemetry do-not-merge/work-in-progress Block merging of a PR because it isn't ready yet. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants