-
Notifications
You must be signed in to change notification settings - Fork 243
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
Document how odo
translates container
component into Kubernetes resources
#6145
Document how odo
translates container
component into Kubernetes resources
#6145
Conversation
✅ Deploy Preview for odo-docusaurus-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
76a774d
to
eab60a7
Compare
The default one makes the highlighted line hardly readable
7d9c44e
to
fdc1dfd
Compare
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.
This is an excellent article, great work, Armel!
I have a few nitpicks that I have suggested. Apart from them, can you ensure you add a period '.' to all the sentences in the tables? I have pointed a few and but not all.
running containers. | ||
Note that synchronization and push to the cluster can also be triggered on demand by pressing `p` at any time. | ||
See [this page](../../command-reference/dev#applying-local-changes-to-the-application-on-the-cluster) for more details. | ||
6. `odo` optionally restarts the running application (if the command is not marked as `hotReloadCapable` in the Devfile). |
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.
This point is not very clear to me. How and when does it restart a running application? Or if this point is a part of point 5, then it makes sense, but then I would merge them both.
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.
Adding more clarification on this.
|
||
By default, `odo` adds the following labels to the Service: | ||
|
||
| Key | Description | Example Value | |
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.
These labels are the same as Deployments, no? Perhaps you don't need to redefine them and simply point to that section?
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.
Yup, they are the same. I'll list them under a dedicated section.
Amazing work, @rm3l! Thanks for putting this together. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dharmit The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
Great work!
|
||
If the Devfile contains any [`Kubernetes` components](../../development/devfile#components) not referenced by any [`apply` command](https://devfile.io/docs/2.2.0-alpha/adding-apply-commands), | ||
`odo dev` automatically applies them. | ||
This is the mechanism used by [`odo add binding`](../../command-reference/add-binding) to have `ServiceBinding` resources created by `odo dev`. |
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.
This is the mechanism used by
odo add binding
to haveServiceBinding
resources created byodo dev
.
You are saying too much, or not enough: you could point to a specific paragraph where this is explained in more details, or remove this part, as it is not clearly understandable as is.
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 was hesitant to add a dedicated section about how odo
handles Devfile kubernetes
components. But you're right, it is currently a bit confusing. Removing this sentence for now - this could be the scope of a separate PR.
This is the mechanism used by [`odo add binding`](../../command-reference/add-binding) to have `ServiceBinding` resources created by `odo dev`. | ||
3. Once the resources are ready, `odo` executes any `build` (optional) and `run` (or `debug`) commands defined in the Devfile into the right containers. | ||
4. It reacts to events occurring in the cluster and that might affect the resources managed. | ||
5. Unless told otherwise (when running `odo dev --no-watch`), `odo` watches for local changes |
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 would move the execption (Unless told otherwise...) later in the sentence, to start with the important thing: odo watches for local changes
|
||
</details> | ||
|
||
#### Volumes |
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 thin kyou should also tell somewhere in the page that odo can also create PersistentVolumeClaim
resources when Volume are defined in Devfile or when Ephemeral is false.
Co-authored-by: Parthvi Vala <pvala@redhat.com> Co-authored-by: Philippe Martin <phmartin@redhat.com>
Kudos, SonarCloud Quality Gate passed! |
/lgtm |
/override OpenShift-Integration-tests/OpenShift-Integration-tests This is a doc-only PR. |
@rm3l: Overrode contexts on behalf of rm3l: OpenShift-Integration-tests/OpenShift-Integration-tests 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/test-infra repository. |
…esources (redhat-developer#6145) * Document how `odo` translates `container` component into Kubernetes resources * Use different background color for highlighted code line The default one makes the highlighted line hardly readable * fixup! Document how `odo` translates `container` component into Kubernetes resources * Apply code review suggestions Co-authored-by: Parthvi Vala <pvala@redhat.com> Co-authored-by: Philippe Martin <phmartin@redhat.com> Co-authored-by: Parthvi Vala <pvala@redhat.com> Co-authored-by: Philippe Martin <phmartin@redhat.com>
What type of PR is this:
/kind documentation
/area documentation
What does this PR do / why we need it:
This adds a new 'Architecture' section under 'Developer Reference' that documents in detail how
odo
works, for users to understand whatodo
does in their clusters.Let me know if I've missed anything, or if you think the structure or style should be different.
Which issue(s) this PR fixes:
Fixes #5174
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer:
Visit https://deploy-preview-6145--odo-docusaurus-preview.netlify.app/docs/development/architecture/how-odo-works