Update current release #120
Open
Conversation
This file contains hidden or 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
* Remove docker from user facing docks * Remove container and docker mentions * Remove SP3 * Add env for wanda * Use vars and upcast rpm * Add explicit sle 16.0
* Fix TRNT-3895 * Add feedback
* Add local docs build * Fix selinux permission * Add workflow guide
* Restructure trento install section * Remove partial as it was included in kubernetes partial * Aligned naming of partial and added revdate to kubernetes
EMaksy
commented
Nov 28, 2025
| :trento: Trento | ||
|
|
||
| == Containerized deployment | ||
| === Containerized deployment |
Member
Author
There was a problem hiding this comment.
Container deployment was moved to developer docs, not to lose the information
EMaksy
commented
Nov 28, 2025
|
|
||
| Follow the steps in <<sec-systemd-deployment>>, but skip the *Install | ||
| Trento using RPM packages* step and follow the procedures as described below. | ||
| Follow the steps in link:https://www.trento-project.io/docs/user-guide/trento-install-server.html#sec-systemd-deployment[systemd installation], but skip the *Install |
Member
Author
There was a problem hiding this comment.
Added a link, to not fight with xref
EMaksy
commented
Nov 28, 2025
| @@ -0,0 +1,36 @@ | |||
| == Local Documentation Preview with Docker | |||
Member
Author
There was a problem hiding this comment.
This part is just developer docs for new way of preview antora with docker
EMaksy
commented
Nov 28, 2025
EMaksy
commented
Nov 28, 2025
| :revdate: 2025-10-16 | ||
|
|
||
|
|
||
| [[sec-trento-k8s-deployment]] |
Member
Author
There was a problem hiding this comment.
Moved to trento-kubernetes-install.adoc[]
EMaksy
commented
Nov 28, 2025
| + | ||
| . Restart the application. | ||
|
|
||
| ==== Enabling OpenID Connect when using Docker images |
Member
Author
There was a problem hiding this comment.
Part of docker mention removal
| + | ||
| . Restart the application. | ||
|
|
||
| [[enabling-oauth-20-when-using-docker-images]] |
Member
Author
There was a problem hiding this comment.
Part of docker mention removal
| + | ||
| . Restart the application. | ||
|
|
||
| ==== Enabling SAML when using Docker images |
Member
Author
There was a problem hiding this comment.
Part of docker mention removal
dmpop
approved these changes
Nov 28, 2025
| [[sec-trento-install-trentoserver-on-existing-k8s-cluster]] | ||
| ==== Installing {trserver} on an existing {k8s} cluster | ||
|
|
||
| {trserver} consists of a several components delivered as container images and intended for deployment on a {k8s} cluster. A manual production-ready deployment of these components requires {k8s} knowledge. Customers without in-house {k8s} expertise and who want to try {trento} with a minimum of effort, can use the {trento} Helm chart. This approach automates the deployment of all the required components on a single {k8s} cluster node. You can use the {trento} Helm chart to install {trserver} on a existing {k8s} cluster as follows: |
Collaborator
There was a problem hiding this comment.
Suggested change
| {trserver} consists of a several components delivered as container images and intended for deployment on a {k8s} cluster. A manual production-ready deployment of these components requires {k8s} knowledge. Customers without in-house {k8s} expertise and who want to try {trento} with a minimum of effort, can use the {trento} Helm chart. This approach automates the deployment of all the required components on a single {k8s} cluster node. You can use the {trento} Helm chart to install {trserver} on a existing {k8s} cluster as follows: | |
| {trserver} consists of a several components delivered as container images and intended for deployment on a {k8s} cluster. A manual production-ready deployment of these components requires {k8s} knowledge. Customers without in-house {k8s} expertise and those who want to try {trento} with a minimum of effort, can use the {trento} Helm chart. This approach automates the deployment of all the required components on a single {k8s} cluster node. You can use the {trento} Helm chart to install {trserver} on a existing {k8s} cluster as follows: |
| [[sec-trento-install-trentoserver-on-k3s]] | ||
| ==== Installing {trserver} on K3s | ||
|
|
||
| If you do not have a {k8s} cluster, or have one but do not want to use it for {trento}, {suse} Rancher's K3s provides an alternative. To deploy {trserver} on K3s, you need a small server or VM (see <<sec-trento-server-requirements>> for minimum requirements) and follow steps in <<pro-trento-manually-installing>>. |
Collaborator
There was a problem hiding this comment.
Suggested change
| If you do not have a {k8s} cluster, or have one but do not want to use it for {trento}, {suse} Rancher's K3s provides an alternative. To deploy {trserver} on K3s, you need a small server or VM (see <<sec-trento-server-requirements>> for minimum requirements) and follow steps in <<pro-trento-manually-installing>>. | |
| If you do not have a {k8s} cluster, or you have one but you do not want to use it for {trento}, you can use {suse} Rancher's K3s as an alternative. To deploy {trserver} on K3s, you need a server or VM (see <<sec-trento-server-requirements>> for minimum requirements) and follow steps in <<pro-trento-manually-installing>>. |
| Sender email for alert notifications | ||
|
|
||
| `ALERTING_RECIPIENT`:: | ||
| Recipient email for alert notifications. |
Collaborator
There was a problem hiding this comment.
Suggested change
| Recipient email for alert notifications. | |
| Email address to receive alert notifications. |
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.
Description
This pr updates the released documentation in the latest branch. I was following our our critical hotfix workflow https://www.trento-project.io/docs/developer/trento-docs-site/collaboration-docs-team/docs-git-workflow.html#_3_applying_a_critical_hotfix.
With this we have also a nice history in the commits :)
When we release Trento 3.0 we will follow this workflow
https://www.trento-project.io/docs/developer/trento-docs-site/collaboration-docs-team/docs-git-workflow.html#_2_publishing_a_new_release
Features