Skip to content
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

docs: k8s dry run section added #1142

Merged
merged 1 commit into from
Oct 21, 2024

Conversation

CodeWithEmad
Copy link
Member

A section will be added to the Kubernetes documentation, explaining the apply command and the benefits of running a dry run before the final deployment.

#1138

docs/k8s.rst Outdated
@@ -116,6 +116,21 @@ All non-persisting data will be deleted, and then re-created.
Common tasks
------------

### Using `tutor k8s apply` with Dry Run
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: this is not rendering as a heading. You might want to try underlining it with =

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch.

docs/k8s.rst Outdated
Comment on lines 121 to 132
The `tutor k8s apply` command serves as a wrapper around `kubectl apply`, allowing you to easily apply your Kubernetes resource configurations stored in `$(tutor config printroot)/env/k8s`. To apply your configurations, simply run::

tutor k8s apply

Before applying changes, you can validate your configurations without making any modifications by using the dry-run option with the server-side validation. Run::

tutor k8s apply --dry-run=server --validate=true

- `--dry-run=server`: This option simulates the application of configurations on the server-side, allowing you to see how Kubernetes would interpret your changes.
- `--validate=true`: This validates your manifests against Kubernetes API standards, helping to catch any errors before applying them.

Utilizing the dry-run feature ensures a more robust deployment process for your Open edX platform on Kubernetes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: We are trying to avoid the usage of you, yours etc. in the docs. The aim is to make the docs generic and not address anyone.

@DawoudSheraz DawoudSheraz merged commit 97e9fa4 into overhangio:master Oct 21, 2024
2 checks passed
@CodeWithEmad CodeWithEmad deleted the fix/dry-run branch October 21, 2024 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

2 participants