Update link to explanation of Operator pattern in Architecture Overview #1216
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…. replaced with what i think is a pretty relevant blog post.
viveksinghggits
approved these changes
Feb 2, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Overview
In the Kanister Architecture Overview Page, in the first paragraph, there is a link to a blog post that explains the operator pattern. The link is out of date. Instead of taking you to a blog post, it just takes you to the main page for red hat's blog. After searching, i believe I've found a suitable blog post that serves as a good explanation of the operator pattern. I've updated the link in the docs/architecture.rst file. here is the new link: https://www.redhat.com/en/blog/operators-over-easy-introduction-kubernetes-operators
Pull request type
Please check the type of change your PR introduces:
Issues
no issue
Test Plan
No tests needed