Repository navigation
Helm install and upgrade - #682
Open
Rachael-Graham wants to merge 3 commits into
Open
Rachael-Graham wants to merge 3 commits into
Rachael-Graham wants to merge 3 commits into
Conversation
Signed-off-by: Rachael Graham <rachael.graham@solo.io>
Contributor
Docs preview
Both are uploaded Worker versions and serve no production traffic. |
Signed-off-by: Rachael Graham <rachael.graham@solo.io>
Rachael-Graham
marked this pull request as ready for review
November 3, 2026 23:03
artberger
approved these changes
Nov 3, 2026
| kubectl logs -n kagent deployment/kagent-controller --previous | grep -i migration | ||
| ``` | ||
|
|
||
| 2. To return to the previous version, restore the database backup that you took in [Prepare to upgrade]({{< link path="operations/upgrade#prepare-to-upgrade" >}}). |
Collaborator
There was a problem hiding this comment.
Is there a command to do this? or do you just go through all the steps again in that linked H2?
|
|
||
| An installation of {{< reuse "kagent-docs/snippets/name-product.md" >}} consists of five Helm releases. Upgrade the releases in the order that you installed them, starting with the CRDs, then Agent Substrate, and then the kagent control plane. | ||
|
|
||
| Upgrade through each release in order, and do not skip a release. For example, to move from 1.0.0 to 1.0.2, upgrade to 1.0.1 first, and then to 1.0.2. To move to a new minor version, upgrade from the last patch release of the previous minor version, such as from 1.0.2 to 1.1.0. To move a 0.10.x installation to 1.x, see [Upgrade from 0.x]({{< link path="operations/upgrade-from-0x" >}}) instead. |
Collaborator
There was a problem hiding this comment.
to move from 1.0.0 to 1.0.2, upgrade to 1.0.1 first, and then to 1.0.2
Just to confirm, is it really patch-specific? At least in other products, it is just minor versions you don't skip.
|
|
||
| Upgrade through each release in order, and do not skip a release. For example, to move from 1.0.0 to 1.0.2, upgrade to 1.0.1 first, and then to 1.0.2. To move to a new minor version, upgrade from the last patch release of the previous minor version, such as from 1.0.2 to 1.1.0. To move a 0.10.x installation to 1.x, see [Upgrade from 0.x]({{< link path="operations/upgrade-from-0x" >}}) instead. | ||
|
|
||
| <!-- REVIEW: kagent is moving from semantic versioning to calendar versioning. The release-order examples in the preceding paragraph, the version variables in "Prepare to upgrade", and the release-order rule itself assume semver. Rewrite them when the calendar version format is published. --> |
Collaborator
There was a problem hiding this comment.
Just to confirm, is the upstream also moving to calver? (this would be different than agentgateway for example)
| --version ${SUBSTRATE_VERSION} \ | ||
| --namespace ate-system --wait | ||
| ``` | ||
|
|
Collaborator
There was a problem hiding this comment.
Maybe add a confirmation step.
| 1. Install the following CLI tools. The kagent CLI runs `helm` to install each chart. | ||
| * [`helm`](https://helm.sh/docs/intro/install/), the Kubernetes package manager. Use Helm 3. | ||
| * [`kubectl`](https://kubernetes.io/docs/tasks/tools/#kubectl), the Kubernetes command line tool. | ||
| * The kagent CLI, matched to the release that these docs cover. |
Collaborator
There was a problem hiding this comment.
Maybe make the formatting match the previous bullets?
Suggested change
| * The kagent CLI, matched to the release that these docs cover. | |
| * `kagent`, the command line tool of the same version as the kagent release that you want to install. |
| --from-literal=ca.crt="${actor_id_ca_root}" | ||
| ``` | ||
|
|
||
| 2. Read the issuer from the cluster, and note which kind it is. Kubernetes distributions advertise different issuers, and the `ate-api-authentication` ConfigMap takes a different form for each kind of issuer. An issuer that does not match the cluster's own is accepted when you create the ConfigMap, and later surfaces as `token issuer ... not trusted` on every `kubectl ate` call. |
Collaborator
There was a problem hiding this comment.
and note which kind it is
maybe a bit more specific; I thought at first this was a CRD kind:
Suggested change
| 2. Read the issuer from the cluster, and note which kind it is. Kubernetes distributions advertise different issuers, and the `ate-api-authentication` ConfigMap takes a different form for each kind of issuer. An issuer that does not match the cluster's own is accepted when you create the ConfigMap, and later surfaces as `token issuer ... not trusted` on every `kubectl ate` call. | |
| 2. Determine whether the issuer for the cluster is an internal or external issuer. Kubernetes distributions advertise different issuers, and the `ate-api-authentication` ConfigMap takes a different form for each kind of issuer. An issuer that does not match the cluster's own is accepted when you create the ConfigMap, and later surfaces as `token issuer ... not trusted` on every `kubectl ate` call. |
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
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.
Uh oh!
There was an error while loading. Please reload this page.