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
Two ali tuts #57
Two ali tuts #57
Conversation
-Deploying and monitoring a Redis cluster to Oracle Container Engine (OKE) -Hosting a private Helm Repository on OCI (Oracle Cloud Infrastructure) with ChartMuseum and OCI Object Storage
Adding links to last week's articles after receiving a msg from JW that neither links back to dev.o. Find that original PR here with those two articles here: #56
|
Signed off by @vagredajr99 . Thanks for reviewing, V! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comments inline.
| date: 2021-12-15 13:34 | ||
| description: Redis, Prometheus, OKE, oh my! | ||
| MRM: WWMK211213P00053 | ||
| author: ali-mukadam |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I may have given confusing instructions, but when the author exists in _authors.yml, the front matter key should be configured as author: AUTHOR_SLUG
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅
deploying-monitoring-redis-oke.md
Outdated
|
|
||
| Get a list of pods and identify the Prometheus pods: | ||
|
|
||
| <!--EDIT there's a line break missing somewhere between grep and prom- but I'm not sure where--> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can remove my HTML comments after editing. Some of these commands appear to be mangled or poorly copy/pasted, please validate against whatever the original source material was.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Corrected this and other goofily-formatted blocks
deploying-monitoring-redis-oke.md
Outdated
|
|
||
| And we will adapt the schema a little bit so we can make use of whatever mimesis provides to create a csv file using Python: | ||
|
|
||
| <!--EDIT: This appears to be mangled python, please validate from source--> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please validate
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Corrected ✅
deploying-monitoring-redis-oke.md
Outdated
|
|
||
| Afterwards, use port-forward to so you can access it using the redis-cli: | ||
|
|
||
| <!--EDIT is there actually a command `k`?--> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There might be a command k, but I'm assuming there's something missing. Please validate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nah, this one is actually exactly faithful to the code block in the article, formatting and all. k isn't an option/flag as far as I can tell.
deploying-monitoring-redis-oke.md
Outdated
|
|
||
| Now import the csv file as follows: | ||
|
|
||
| <!--EDIT appears mangled, assume line break in --pipe\nAll, and no line break before file.csv--> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went ahead and modified this one so it made sense to me, but please double check it against source.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My new commit matches formatting form the source
deploying-monitoring-redis-oke.md
Outdated
|
|
||
| However, when you use Terraform to do the provisioning, you will need to explicitly set the order as follows: | ||
|
|
||
| <!--EDIT please verify indentation--> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like everything after the first line should be outdented one tab-width, but I defer to article's original formatting. Please verify.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For this one, I actually did match it to article's formatting (though I did add a space I missed btwn the first code block and the next line).
The description key for the Redis article is a little cheeky, but I think we can get away with it since the article title is descriptive. If you don't think it can work, let's try:
That maybe too long, though. LMK.
Otherwise, I got a message from JW to provide backlinks to my articles from last week, so I added some contents in those articles' front matter to visit dev.o.