Repository navigation
Conversation
…ble fields in `spec`
…during bootstrap
Also adjust machinetemplate reference for v1beta1 Needs siderolabs/cluster-api-control-plane-provider-talos#251 or equivalent.
Update component defaults and rewrite non-prefixed versions.
TODO: figture out if/how we want to allow users to adjust the patches.
This field is required for Tuppr to be able to perform upgrades.
And set default to `Oldest`
We default to patch version `0` for `install.image` in the MachineConfig. This should be unproblematic since the field only needs to be present in order for Tuppr to be able to determine the base image for upgrades and the whole `install` section has no effect on machines created from the OpenStack raw base image.
…figuration` Tested that this config works on Talos 1.13. Note that on Talos 1.14 we should get a real MachineConfiguration field for `AuthenticationConfiguration`. We can't write to one of the already mounted directories of the K8s API server pods, so we write our config file to `/var/config/kubernetes/kube-apiserver` and mount that directory in the API server pods.
simu
force-pushed
the
tmp/user-kubeconfig
branch
7 times, most recently
from
August 12, 2026 11:55
af95a87 to
b90b635
Compare
CAPI auto-generates the selector and when switching to server-side apply we can't have an explicit `matchLabels: null` anymore.
simu
force-pushed
the
tmp/user-kubeconfig
branch
from
August 13, 2026 07:09
70d7541 to
300fcf3
Compare
This is required for metrics-server, but requires a mechanism to approve Kubelet CSRs. We currently use https://github.com/alex1989hu/kubelet-serving-cert-approver
TODO: move this to capi-core component?
simu
force-pushed
the
initial-implementation
branch
from
August 13, 2026 07:19
ccb535c to
8c94468
Compare
simu
force-pushed
the
tmp/user-kubeconfig
branch
4 times, most recently
from
August 14, 2026 11:39
d3d9192 to
b75da31
Compare
simu
force-pushed
the
tmp/user-kubeconfig
branch
from
August 14, 2026 11:40
b75da31 to
84dd5f7
Compare
7 tasks done
simu
force-pushed
the
initial-implementation
branch
from
September 11, 2026 12:34
52b8f99 to
152f37b
Compare
Member
Author
|
user-kubeconfig server moved to capi-core. TBD what we do with the CA dynamic fact. |
Member
Author
|
CA dynfact now in projectsyn/component-capi-provider-talos#12 so we don't need this draft PR anymore. |
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
1 participant
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.
TODO
user-kubeconfigdeployment for the config hash annotation managed by Espejote (can we just switch to SSA?)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.