Repository navigation
Release/3.9.0 - #3
Merged
Merged
Conversation
Raise SDK to v3.9.0-rc.2, operator to v3.9.0-rc.1, and align controller, router, NATS, and edgelet pins in versions.mk.
Drop deviceScanFrequency, bluetoothEnabled, and abstractedHardwareEnabled from agent sync, edgelet config, testdata, and functional tests. Map new fog status fields from the v3.9 SDK.
Replace isSecure, requiresCert, and certificate with type (oci|hf), ca, and insecure. Make registry email optional and extend agent status fields on resource types.
Add JSON create/update executors, kind dispatch, deploy order after Registry, and root-level RuntimeClass handler parsing.
Resolve agent names to fog UUIDs and call Controller link APIs with volume-mount-style commands.
…microservice templates Expose list and detail commands with correct RuntimeClass root handler YAML and model uuid on describe.
Support spec.template and spec.models on deploy, catalog-only PATCH via --patch-model, and describe microservice and agent v3.9 fields including podId and parsed model status.
…t all Filter Failed, Succeeded, and terminating controller pods, stop persisting them in namespace config, and include a models table in get all.
Record HAL and registry removals, new v3.9 resources, patch-model, and get controllers fix in the changelog and deploy help output.
…commands Add model, runtimeclass, and microservice-template subcommand pages and refresh parent command help for both iofogctl and potctl.
Print lastError, lastErrorAt, and restartCount on get/describe from SDK v3.9.0-rc.3. Pair Controller 3.9.0-rc.3 and edgelet 1.1.0-rc.2.
Pick up SDK volume-mapping scope (private|shared) via iofog-go-sdk v3.9.0-rc.4, and pair the CLI with controller 3.9.0-rc.5 and edgelet 1.1.0-rc.3.
Pick up Knowledge plus host-status types, and align Controller 3.9.0-rc.9 and edgelet 1.1.0-rc.5 with the new agent drain path.
Create or update Knowledge through JSON CRUD, place it after Model in multi-doc order, and allow catalog-only microservice patches, including together with --patch-model.
Resolve agent names to UUIDs and link or unlink Knowledge the same way Models already do.
List Knowledge in its own table and in get all, show linked agents on describe, and surface Controller errors on delete.
Keep spec.knowledge on the microservice YAML path next to spec.models so both catalogs round-trip on deploy.
Parse Knowledge status and fix millisecond timestamps, print host fog metrics in a stable field order, and show cpuUsage as cores (100 = 1 core) for agents and microservices.
… OTA. Keep control up, drain with the staged binary, and write the install receipt only after services return so a failed drain does not reap workloads or leave volume locks.
Regenerate CLI reference for the new Knowledge surfaces and record the rc.4 Knowledge, describe, and pin changes.
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.
No description provided.