Publish a blog post - deploy-python-pipeline-on-flink-runner

[jaehyeon-kim]

Please add a meaningful description for your change here

Publish a new blog post titled Deploy Python Pipelines on Kubernetes via the Flink Runner.

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @rszper for label website.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[liferoad]

Thanks for the blog!

https://apache-beam-website-pull-requests.storage.googleapis.com/31655/blog/deploy-python-pipeline-on-flink-runner/index.html has the staged file. Looks great!

[liferoad]

@rszper Could you review the blog? Thanks!

[liferoad]

@damondouglas FYI.

[damondouglas]

@jaehyeon-kim thank you for working on this. Could you work with @rszper and resolve any unresolved comments so we know when this is ready for merge? I'll have a look at it myself after comments resolve.

[jaehyeon-kim]

Hi @rszper

I just found the python code block hides code snippets and it is changed from using {{< highlight py >}} to ```python. The applicable lines start at 273, 507, and 762.

[github-actions]

R: @kennknowles for final approval

[kennknowles]

R: @liferoad

you are now a committer :-)

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control

[liferoad]

I am going to wait for @damondouglas to take a quick look. Thanks.

[Abacn]

when there are many commits sometimes it is good to use "squash and merge" otherwise the git log flood with the intermediate commits - https://github.com/apache/beam/commits/master/?before=c1c853fcc520e8519dd0baf19d7714f345979bcc+35

[kennknowles]

If you use git commit --fixup HEAD then it will make very obvious commit messages. We could/should have GHA checks or something that go red when there are non-desired commits in the PR. We should still support multi-commit PRs but only if they are organized into meaningful commits. Maybe the description can tag #multicommit or something.