Deploy a Tuppr TalosUpgrade custom resource - #3
Merged
Merged
Conversation
simu
force-pushed
the
feat/tuppr-talosupgrade
branch
2 times, most recently
from
September 14, 2026 12:34
0670601 to
6770aa6
Compare
simu
force-pushed
the
feat/tuppr-talosupgrade
branch
from
September 14, 2026 12:55
6770aa6 to
a6353b2
Compare
simu
force-pushed
the
feat/tuppr-talosupgrade
branch
from
September 15, 2026 09:51
a6353b2 to
f5f444a
Compare
simu
force-pushed
the
feat/tuppr-talosupgrade
branch
from
September 16, 2026 09:37
f5f444a to
1c3432c
Compare
simu
force-pushed
the
feat/tuppr-talosupgrade
branch
from
September 16, 2026 09:47
1c3432c to
fc800a8
Compare
simu
added this pull request to stack #6
September 16, 2026 09:47
simu
force-pushed
the
feat/tuppr-talosupgrade
branch
from
September 16, 2026 09:50
fc800a8 to
ea57f55
Compare
simu
force-pushed
the
feat/tuppr-talosupgrade
branch
from
September 16, 2026 14:13
ea57f55 to
d0844b0
Compare
HappyTetrahedron
approved these changes
Sep 17, 2026
simu
force-pushed
the
feat/tuppr-talosupgrade
branch
2 times, most recently
from
September 17, 2026 11:53
d150a1d to
b2417a8
Compare
Note that we can only configure `kubernetesTalosAPIAccess` in the `MachineConfiguration` for Talos control plane nodes. Trying to configure `kubernetesTalosAPIAccess` on worker nodes results in the following error when bootstrapping nodes: ``` failed to validate config acquired via platform openstack: 1 error occurred: * v1alpha1.Config: 1 error occurred: * feature Kubernetes Talos API Access can only be enabled on control plane machines ```
We will use the patch version only for configuring the Tuppr `TalosUpgrade`.
This ensures that we have explicit control over apply order between CAPI and Tuppr resources and reduces the amount of correlated config scattered across different components.
simu
force-pushed
the
feat/tuppr-talosupgrade
branch
from
September 17, 2026 18:24
b2417a8 to
f6cb43c
Compare
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
2 participants
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.
We use Tuppr to do Talos patch upgrades without having to upload new base images and replace nodes. Tuppr is configured through the
TalosUpgradecustom resource which is rendered by this PR.By managing the
TalosUpgradein this component, we have explicit control over apply order between CAPI and Tuppr resources and reduce the amount of correlated config scattered across different components.Because we need to know the Talos patch version, the PR also changes the component to expect a full Talos version (
<major>.<minor>.<patch>) in parametertalosVersion. Note that the user-supplied patch version is only used by the TupprTalosUpgrade.Checklist
changelog.
The PR has a meaningful description that sums up the change. It will be
linked in the changelog.
bug,enhancement,documentation,change,breaking,dependencyas they show up in the changelog.