Creating a Fully Managed Beam Streaming System with Flink Runner on Kubernetes - Part 2

[talatuyarer]

Hi all,

I created part 2 of the blog post. Could you review this ?

Thanks

---

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]

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

[talatuyarer]

Hi
@rszper and @damondouglas Could you review my part 2 blog post ? After this I will also share last part How to build Autoscaling for Apache Beam Job sections. I am working on it.

[damondouglas]

@talatuyarer Thank you again for doing this! I will be happy to review this.

[talatuyarer]

@talatuyarer Thank you again for doing this! I will be happy to review this.

Thank you @damondouglas I look forward your comments.

[rszper]

I'm learning so much!

[talatuyarer]

I'm learning so much!

Thank you so much @rszper. I a m learning so much from your comments too

[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).

[rszper]

A few more comments, mostly minor. Otherwise, looks good.

[rszper]

Looks great!

[talatuyarer]

@rszper and @damondouglas I will it is ready to publish. If you dont have anything. I addressed all @rszper 's suggestions

[github-actions]

R: @melap for final approval

[damondouglas]

Thank you for all your help and comments, @rszper! I see the bot assigned @melap for final approval. Is there a suggested approval I don't know about or can we go ahead and squash/merge?

My only non-blocking comment is for those who learn by doing, it would be great if there were published Kubernetes manifests or step-by-step guide for someone to replicate the environment setup discussed in this blog. I remember part 1 has the Deployment manifest but I'm not sure this is enough nor have I tried on my own Kubernetes cluster.