yolokube/traefik-certmanager
yolokube/traefik-certmanager
Archived
3
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

fix(kubernetes): temporary solution for updated k8s python client
All checks were successful
ci/woodpecker/push/build Pipeline was successful
Details
ci/woodpecker/push/deploy Pipeline was successful
Details

Browse source
This commit is contained in:
Tom Neuber 2025-01-05 00:21:36 +01:00
parent 07d6fe7442
commit 977b5bca85
Signed by: tom
GPG key ID: F17EFE4272D89FF6
1477 changed files with 422337 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

14
kubernetes/docs/V1NodeConfigStatus.md Normal file
View file

@ -0,0 +1,14 @@
# V1NodeConfigStatus
NodeConfigStatus describes the status of the config assigned by Node.Spec.ConfigSource.
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**active** | [**V1NodeConfigSource**](V1NodeConfigSource.md) | | [optional]
**assigned** | [**V1NodeConfigSource**](V1NodeConfigSource.md) | | [optional]
**error** | **str** | Error describes any problems reconciling the Spec.ConfigSource to the Active config. Errors may occur, for example, attempting to checkpoint Spec.ConfigSource to the local Assigned record, attempting to checkpoint the payload associated with Spec.ConfigSource, attempting to load or validate the Assigned config, etc. Errors may occur at different points while syncing config. Earlier errors (e.g. download or checkpointing errors) will not result in a rollback to LastKnownGood, and may resolve across Kubelet retries. Later errors (e.g. loading or validating a checkpointed config) will result in a rollback to LastKnownGood. In the latter case, it is usually possible to resolve the error by fixing the config assigned in Spec.ConfigSource. You can find additional information for debugging by searching the error message in the Kubelet log. Error is a human-readable description of the error state; machines can check whether or not Error is empty, but should not rely on the stability of the Error text across Kubelet versions. | [optional]
**last_known_good** | [**V1NodeConfigSource**](V1NodeConfigSource.md) | | [optional]
[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)