Blog post - Istio Vulnerability Scanner tool

[chaltenio]

Description

Blog post announcement - Free Istio Vulnerability Scanner tool.

Reviewers

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

[istio-policy-bot]

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

[linux-foundation-easycla[bot]]

• :x: - login: @chaltenio / name: Ch Mzr . The commit (0ab2ed52bbc69b569f60d627d7c1f5af1a19bcec, a58aa409ffecd51173fad9d538b53bc6a7a4fd92, 0421ced144eca870984bc4a6cb23cf1f3d4f9122) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[istio-testing]

Hi @chaltenio. 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/test-infra repository.

[linsun]

/hold

The steering committee is discussing if this is appropriate to post as a blog.

[istio-testing]

@chaltenio: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
lint_istio.io	0421ced144eca870984bc4a6cb23cf1f3d4f9122	link	true	/test lint

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/test-infra repository. I understand the commands that are listed here.

[linsun]

I saw @craigbox closed this without comment, was not sure if the feedback was provided to the PR author. For transparency, steering has discussed this blog and don't think we should publish it in istio.io.

[craigbox]

The feedback was provided :)

[chaltenio]

Thanks for the update folks. I would appreciate it if you could establish guidelines for blog posts so that we know what is allowed and what is not next time.

Regarding those steering discussions, are they recorded and uploaded on Youtube for transparency? Cheers

[craigbox]

No, they're not. We have thoughts on how to improve the process.

Guidelines are definitely on the backlog.