WIP: Updating k8s - #11
Open
bstoll wants to merge 19 commits into
Open
Conversation
Coverage Report for CI Build 33810315031Coverage increased (+0.2%) to 43.703%Details
Uncovered Changes
Coverage Regressions4 previously-covered lines in 3 files lost coverage.
Coverage Stats
💛 - Coveralls |
* - new ixia-c operator - new ixiatg configmap - removed all the rbac-proxy lines from ceos, srlinux and lemming controllers * lemming controller restored * style: format manifests with prettier to pass super-linter --------- Co-authored-by: Brandon Stoll <bstoll@users.noreply.github.com>
This pulls the current meshnet image so it's static in the packer image, similar to what is done for other images used by KNE. That will keep meshnet stable for a given KNE machine image, rather that tracking to the floating ga tag.
bstoll
force-pushed
the
update-k8s-v1.36
branch
from
August 25, 2026 20:47
25ad2a2 to
cf2cdf7
Compare
…validation - Update default Kubernetes version to v1.36.1 and kind node image to kindest/node:v1.36.1 - Update kind CLI dependency to v0.32.0 in .mk/kind.mk, deployment configs, and packer specs - Update packer configurations to use Kubernetes v1.36 apt repository - Add KubernetesVersion field to KubeadmSpec and wire it through controller proto, server, and kubeadm init configuration generator - Add cluster server version validation during deployment to ensure deployed API server matches configured version spec - Update meshnet daemonset nodeSelector label to standard kubernetes.io/arch - Add dynamic host package synchronization in kne_test.sh based on packer configuration
bstoll
force-pushed
the
update-k8s-v1.36
branch
from
August 25, 2026 20:59
cf2cdf7 to
9641548
Compare
) * Shift to using dynamic.Interface for meshnet and lemming This is consistent with what we do for vendor images. (Cisco, Juniper, Nokia, Arista.) It reduces the number of indirect dependencies we pick up on K8s API libraries, which simplifies life within Google's monorepo. Functionally, it changes nothing. * Specify Kind in dynamic Lemming API
* replace more instances of clientset with dynamic client Shift to using dynamic.Interface for meshnet and lemming. I seem to have missed some instances of this in my prior PR. This is consistent with what we do for vendor images. (Cisco, Juniper, Nokia, Arista.) It reduces the number of indirect dependencies we pick up on K8s API libraries, which simplifies life within Google's monorepo. Functionally, it changes nothing. * Lint fixes
This picks up key changes: * Fix controller workqueue rate limits (faster lemming startup) * Don't allocate nodeports for lemming k8s services (like other KNE-created services)
…d response validation for JunOS / cPTX nodes in KNE. (openconfig#763) Refine KNE Juniper node error handling, cert idempotency, and response lookup - Fix RE2 regex matching with isJunosError using multi-line and case-insensitive mode `(?im)(\berror:|\bcommit error\b|\bsyntax error\b)`. This prevents false positives on configuration keywords/descriptions while capturing all JunOS error phrasings. - Handle 'already exists' output idempotently in waitCertInfraReadyAndPushCert so node reuses and pod restarts do not trigger 15-minute retry timeout loops. - Dynamically locate the response matching the generate-self-signed command to avoid premature exit when the preceding key-pair generation returns successfully. - Fix log variable mismatch in waitConfigInfraReadyAndPushConfigs (use configModeRetrySleep instead of certGenRetrySleep). - Add unit tests in juniper_test.go covering isJunosError regex cases, idempotent restarts, and a dedicated testdata fixture for key-success/cert-failure scenarios.
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
7 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.
No description provided.