Initial implementation - #1
Merged
Merged
Conversation
simu
force-pushed
the
initial-implementation
branch
4 times, most recently
from
June 25, 2026 09:10
33a79b5 to
ac3dd81
Compare
simu
force-pushed
the
initial-implementation
branch
4 times, most recently
from
July 6, 2026 07:42
6a9ca4d to
588e0f0
Compare
simu
force-pushed
the
initial-implementation
branch
5 times, most recently
from
August 3, 2026 15:47
4872063 to
f301c81
Compare
simu
force-pushed
the
initial-implementation
branch
from
August 13, 2026 07:19
ccb535c to
8c94468
Compare
…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.
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
simu
force-pushed
the
initial-implementation
branch
from
September 11, 2026 12:34
52b8f99 to
152f37b
Compare
Note that this commit removes the explicit namespace from a bunch of manifests. This isn't an issue when applying the config via ArgoCD (which is configured with the correct target namespace), and we account for the missing namespace in the manifests by explicitly using `kubectl apply -n syn-cluster-api` in the install workflow.
Also remove note regarding upgrades.
simu
marked this pull request as ready for review
September 16, 2026 09:33
simu
added this pull request to stack #6
September 16, 2026 09:47
simu
force-pushed
the
initial-implementation
branch
from
September 16, 2026 14:13
2e208b8 to
4de862e
Compare
HappyTetrahedron
approved these changes
Sep 17, 2026
HappyTetrahedron
left a comment
HappyTetrahedron
left a comment
There was a problem hiding this comment.
LGTM overall; there was one part I didn't understand, question inline.
simu
force-pushed
the
initial-implementation
branch
from
September 17, 2026 11:53
079d062 to
0de5260
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.
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.