-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Rewrite Configuring Redis using a ConfigMap #48716
base: main
Are you sure you want to change the base?
Rewrite Configuring Redis using a ConfigMap #48716
Conversation
Rewrote the following documents for clarity: - Configuring Redis using a ConfigMap - Prerequisites doc
Welcome @jerry-li-dev! |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Restest please |
/retest |
Fix grammar issue
@jerry-li-dev, Can you try to force push the commit and see if error can fix. |
Below are the commands you need to execute to trigger the build again:
|
Fix grammar issue
…com/jerry-li-dev/website into rewrite-config-redis-with-configmap
/retest |
@jerry-li-dev: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
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-sigs/prow repository. |
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.
We cannot retrigger Netlify builds with /ok-to-test
Prow command.
Instead, you can use this method.
But the point is that the build error occurs because there exists an error in this PR.
Netlify build log is saying that:
Error: error building site: process: readAndProcessContent: "/opt/build/repo/content/en/includes/task-tutorial-prereqs.md:1:1": invalid YAML delimiter
- If you do not already have a cluster, you can create one by using [minikube](https://minikube.sigs.k8s.io/docs/tutorials/multi_node/) or you can use one of these Kubernetes playgrounds: | ||
- [Killercoda](https://killercoda.com/playgrounds/scenario/kubernetes) | ||
- [Play with Kubernetes](https://labs.play-with-k8s.com/) | ||
|
||
* [Killercoda](https://killercoda.com/playgrounds/scenario/kubernetes) | ||
* [Play with Kubernetes](https://labs.play-with-k8s.com/) | ||
* Understand how to [configure a Pod to use a ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/). |
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 suggest you to preserve the task-tutorial-prereqs.md
as-is, not modifying in this PR.
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.
The formatting in the current task tutorial file is not usable. It has to be changed.
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.
Hi Jerry, you should clarify how it's not usable in your PR description and why the change is important.
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.
Existing formatting seems fine to me, so an explanation of why you find it not usable would be helpful.
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.
Most of this is just rewording existing content without materially changing much. More details as to why you want to make these changes and what is wrong with the existing content would be good to add to the description.
|
||
## What you'll learn |
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.
Is there a reason for moving away from the conventional Objectives section heading?
|
||
* Create a ConfigMap with Redis configuration values | ||
* Create a Redis Pod that mounts and uses the created ConfigMap | ||
* Verify that the configuration was correctly applied. | ||
|
||
## Requirements |
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.
Here too, why move away from the standardized prerequisites block?
|
||
- Kubernetes cluster | ||
- kubectl command-line tool (`kubectl` 1.14 and above) configured to communicate with your cluster. |
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 this statement is misleading. It implies you could use kubectl 1.14, but that is not correct for most users today. A specific version reference could probably be dropped here since 1.14 (and many more of the later ones) are well end of life by this point.
|
||
<!-- lessoncontent --> | ||
|
||
## 1. Create a Redis ConfigMap |
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 don't think we want to use bullet number is section headers.
- If you do not already have a cluster, you can create one by using [minikube](https://minikube.sigs.k8s.io/docs/tutorials/multi_node/) or you can use one of these Kubernetes playgrounds: | ||
- [Killercoda](https://killercoda.com/playgrounds/scenario/kubernetes) | ||
- [Play with Kubernetes](https://labs.play-with-k8s.com/) | ||
|
||
* [Killercoda](https://killercoda.com/playgrounds/scenario/kubernetes) | ||
* [Play with Kubernetes](https://labs.play-with-k8s.com/) | ||
* Understand how to [configure a Pod to use a ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/). |
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.
Existing formatting seems fine to me, so an explanation of why you find it not usable would be helpful.
Description
Rewrote the following documents for clarity:
Issue
Closes: #