Package io.kubernetes.client.proto

Class V1.NodeConfigStatus.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessageV3.Builder<V1.NodeConfigStatus.Builder>
io.kubernetes.client.proto.V1.NodeConfigStatus.Builder
All Implemented Interfaces:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, V1.NodeConfigStatusOrBuilder, Cloneable
Enclosing class:
V1.NodeConfigStatus
public static final class V1.NodeConfigStatus.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<V1.NodeConfigStatus.Builder> implements V1.NodeConfigStatusOrBuilder
 NodeConfigStatus describes the status of the config assigned by Node.Spec.ConfigSource.
Protobuf type k8s.io.api.core.v1.NodeConfigStatus

  • Method Details

    • getDescriptor

      public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

    • internalGetFieldAccessorTable

      protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
      Specified by:
      internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<V1.NodeConfigStatus.Builder>

    • clear

      public V1.NodeConfigStatus.Builder clear()
      Specified by:
      clear in interface com.google.protobuf.Message.Builder
      Specified by:
      clear in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clear in class com.google.protobuf.GeneratedMessageV3.Builder<V1.NodeConfigStatus.Builder>

    • getDescriptorForType

      public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
      Specified by:
      getDescriptorForType in interface com.google.protobuf.Message.Builder
      Specified by:
      getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
      Overrides:
      getDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<V1.NodeConfigStatus.Builder>

    • getDefaultInstanceForType

      public V1.NodeConfigStatus getDefaultInstanceForType()
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

    • build

      public V1.NodeConfigStatus build()
      Specified by:
      build in interface com.google.protobuf.Message.Builder
      Specified by:
      build in interface com.google.protobuf.MessageLite.Builder

    • buildPartial

      public V1.NodeConfigStatus buildPartial()
      Specified by:
      buildPartial in interface com.google.protobuf.Message.Builder
      Specified by:
      buildPartial in interface com.google.protobuf.MessageLite.Builder

    • clone

      public V1.NodeConfigStatus.Builder clone()
      Specified by:
      clone in interface com.google.protobuf.Message.Builder
      Specified by:
      clone in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clone in class com.google.protobuf.GeneratedMessageV3.Builder<V1.NodeConfigStatus.Builder>

    • setField

      public V1.NodeConfigStatus.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      Specified by:
      setField in interface com.google.protobuf.Message.Builder
      Overrides:
      setField in class com.google.protobuf.GeneratedMessageV3.Builder<V1.NodeConfigStatus.Builder>

    • clearField

      public V1.NodeConfigStatus.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field)
      Specified by:
      clearField in interface com.google.protobuf.Message.Builder
      Overrides:
      clearField in class com.google.protobuf.GeneratedMessageV3.Builder<V1.NodeConfigStatus.Builder>

    • clearOneof

      public V1.NodeConfigStatus.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)
      Specified by:
      clearOneof in interface com.google.protobuf.Message.Builder
      Overrides:
      clearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<V1.NodeConfigStatus.Builder>

    • setRepeatedField

      public V1.NodeConfigStatus.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value)
      Specified by:
      setRepeatedField in interface com.google.protobuf.Message.Builder
      Overrides:
      setRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<V1.NodeConfigStatus.Builder>

    • addRepeatedField

      public V1.NodeConfigStatus.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      Specified by:
      addRepeatedField in interface com.google.protobuf.Message.Builder
      Overrides:
      addRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<V1.NodeConfigStatus.Builder>

    • mergeFrom

      public V1.NodeConfigStatus.Builder mergeFrom(com.google.protobuf.Message other)
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<V1.NodeConfigStatus.Builder>

    • mergeFrom

      public V1.NodeConfigStatus.Builder mergeFrom(V1.NodeConfigStatus other)

    • isInitialized

      public final boolean isInitialized()
      Specified by:
      isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
      Overrides:
      isInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<V1.NodeConfigStatus.Builder>

    • mergeFrom

      public V1.NodeConfigStatus.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Specified by:
      mergeFrom in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<V1.NodeConfigStatus.Builder>
      Throws:
      IOException

    • hasAssigned

      public boolean hasAssigned()
       Assigned reports the checkpointed config the node will try to use.
 When Node.Spec.ConfigSource is updated, the node checkpoints the associated
 config payload to local disk, along with a record indicating intended
 config. The node refers to this record to choose its config checkpoint, and
 reports this record in Assigned. Assigned only updates in the status after
 the record has been checkpointed to disk. When the Kubelet is restarted,
 it tries to make the Assigned config the Active config by loading and
 validating the checkpointed payload identified by Assigned.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource assigned = 1;
      Specified by:
      hasAssigned in interface V1.NodeConfigStatusOrBuilder

    • getAssigned

      public V1.NodeConfigSource getAssigned()
       Assigned reports the checkpointed config the node will try to use.
 When Node.Spec.ConfigSource is updated, the node checkpoints the associated
 config payload to local disk, along with a record indicating intended
 config. The node refers to this record to choose its config checkpoint, and
 reports this record in Assigned. Assigned only updates in the status after
 the record has been checkpointed to disk. When the Kubelet is restarted,
 it tries to make the Assigned config the Active config by loading and
 validating the checkpointed payload identified by Assigned.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource assigned = 1;
      Specified by:
      getAssigned in interface V1.NodeConfigStatusOrBuilder

    • setAssigned

      public V1.NodeConfigStatus.Builder setAssigned(V1.NodeConfigSource value)
       Assigned reports the checkpointed config the node will try to use.
 When Node.Spec.ConfigSource is updated, the node checkpoints the associated
 config payload to local disk, along with a record indicating intended
 config. The node refers to this record to choose its config checkpoint, and
 reports this record in Assigned. Assigned only updates in the status after
 the record has been checkpointed to disk. When the Kubelet is restarted,
 it tries to make the Assigned config the Active config by loading and
 validating the checkpointed payload identified by Assigned.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource assigned = 1;

    • setAssigned

      public V1.NodeConfigStatus.Builder setAssigned(V1.NodeConfigSource.Builder builderForValue)
       Assigned reports the checkpointed config the node will try to use.
 When Node.Spec.ConfigSource is updated, the node checkpoints the associated
 config payload to local disk, along with a record indicating intended
 config. The node refers to this record to choose its config checkpoint, and
 reports this record in Assigned. Assigned only updates in the status after
 the record has been checkpointed to disk. When the Kubelet is restarted,
 it tries to make the Assigned config the Active config by loading and
 validating the checkpointed payload identified by Assigned.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource assigned = 1;

    • mergeAssigned

      public V1.NodeConfigStatus.Builder mergeAssigned(V1.NodeConfigSource value)
       Assigned reports the checkpointed config the node will try to use.
 When Node.Spec.ConfigSource is updated, the node checkpoints the associated
 config payload to local disk, along with a record indicating intended
 config. The node refers to this record to choose its config checkpoint, and
 reports this record in Assigned. Assigned only updates in the status after
 the record has been checkpointed to disk. When the Kubelet is restarted,
 it tries to make the Assigned config the Active config by loading and
 validating the checkpointed payload identified by Assigned.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource assigned = 1;

    • clearAssigned

      public V1.NodeConfigStatus.Builder clearAssigned()
       Assigned reports the checkpointed config the node will try to use.
 When Node.Spec.ConfigSource is updated, the node checkpoints the associated
 config payload to local disk, along with a record indicating intended
 config. The node refers to this record to choose its config checkpoint, and
 reports this record in Assigned. Assigned only updates in the status after
 the record has been checkpointed to disk. When the Kubelet is restarted,
 it tries to make the Assigned config the Active config by loading and
 validating the checkpointed payload identified by Assigned.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource assigned = 1;

    • getAssignedBuilder

      public V1.NodeConfigSource.Builder getAssignedBuilder()
       Assigned reports the checkpointed config the node will try to use.
 When Node.Spec.ConfigSource is updated, the node checkpoints the associated
 config payload to local disk, along with a record indicating intended
 config. The node refers to this record to choose its config checkpoint, and
 reports this record in Assigned. Assigned only updates in the status after
 the record has been checkpointed to disk. When the Kubelet is restarted,
 it tries to make the Assigned config the Active config by loading and
 validating the checkpointed payload identified by Assigned.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource assigned = 1;

    • getAssignedOrBuilder

      public V1.NodeConfigSourceOrBuilder getAssignedOrBuilder()
       Assigned reports the checkpointed config the node will try to use.
 When Node.Spec.ConfigSource is updated, the node checkpoints the associated
 config payload to local disk, along with a record indicating intended
 config. The node refers to this record to choose its config checkpoint, and
 reports this record in Assigned. Assigned only updates in the status after
 the record has been checkpointed to disk. When the Kubelet is restarted,
 it tries to make the Assigned config the Active config by loading and
 validating the checkpointed payload identified by Assigned.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource assigned = 1;
      Specified by:
      getAssignedOrBuilder in interface V1.NodeConfigStatusOrBuilder

    • hasActive

      public boolean hasActive()
       Active reports the checkpointed config the node is actively using.
 Active will represent either the current version of the Assigned config,
 or the current LastKnownGood config, depending on whether attempting to use the
 Assigned config results in an error.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource active = 2;
      Specified by:
      hasActive in interface V1.NodeConfigStatusOrBuilder

    • getActive

      public V1.NodeConfigSource getActive()
       Active reports the checkpointed config the node is actively using.
 Active will represent either the current version of the Assigned config,
 or the current LastKnownGood config, depending on whether attempting to use the
 Assigned config results in an error.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource active = 2;
      Specified by:
      getActive in interface V1.NodeConfigStatusOrBuilder

    • setActive

      public V1.NodeConfigStatus.Builder setActive(V1.NodeConfigSource value)
       Active reports the checkpointed config the node is actively using.
 Active will represent either the current version of the Assigned config,
 or the current LastKnownGood config, depending on whether attempting to use the
 Assigned config results in an error.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource active = 2;

    • setActive

      public V1.NodeConfigStatus.Builder setActive(V1.NodeConfigSource.Builder builderForValue)
       Active reports the checkpointed config the node is actively using.
 Active will represent either the current version of the Assigned config,
 or the current LastKnownGood config, depending on whether attempting to use the
 Assigned config results in an error.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource active = 2;

    • mergeActive

      public V1.NodeConfigStatus.Builder mergeActive(V1.NodeConfigSource value)
       Active reports the checkpointed config the node is actively using.
 Active will represent either the current version of the Assigned config,
 or the current LastKnownGood config, depending on whether attempting to use the
 Assigned config results in an error.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource active = 2;

    • clearActive

      public V1.NodeConfigStatus.Builder clearActive()
       Active reports the checkpointed config the node is actively using.
 Active will represent either the current version of the Assigned config,
 or the current LastKnownGood config, depending on whether attempting to use the
 Assigned config results in an error.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource active = 2;

    • getActiveBuilder

      public V1.NodeConfigSource.Builder getActiveBuilder()
       Active reports the checkpointed config the node is actively using.
 Active will represent either the current version of the Assigned config,
 or the current LastKnownGood config, depending on whether attempting to use the
 Assigned config results in an error.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource active = 2;

    • getActiveOrBuilder

      public V1.NodeConfigSourceOrBuilder getActiveOrBuilder()
       Active reports the checkpointed config the node is actively using.
 Active will represent either the current version of the Assigned config,
 or the current LastKnownGood config, depending on whether attempting to use the
 Assigned config results in an error.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource active = 2;
      Specified by:
      getActiveOrBuilder in interface V1.NodeConfigStatusOrBuilder

    • hasLastKnownGood

      public boolean hasLastKnownGood()
       LastKnownGood reports the checkpointed config the node will fall back to
 when it encounters an error attempting to use the Assigned config.
 The Assigned config becomes the LastKnownGood config when the node determines
 that the Assigned config is stable and correct.
 This is currently implemented as a 10-minute soak period starting when the local
 record of Assigned config is updated. If the Assigned config is Active at the end
 of this period, it becomes the LastKnownGood. Note that if Spec.ConfigSource is
 reset to nil (use local defaults), the LastKnownGood is also immediately reset to nil,
 because the local default config is always assumed good.
 You should not make assumptions about the node's method of determining config stability
 and correctness, as this may change or become configurable in the future.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource lastKnownGood = 3;
      Specified by:
      hasLastKnownGood in interface V1.NodeConfigStatusOrBuilder

    • getLastKnownGood

      public V1.NodeConfigSource getLastKnownGood()
       LastKnownGood reports the checkpointed config the node will fall back to
 when it encounters an error attempting to use the Assigned config.
 The Assigned config becomes the LastKnownGood config when the node determines
 that the Assigned config is stable and correct.
 This is currently implemented as a 10-minute soak period starting when the local
 record of Assigned config is updated. If the Assigned config is Active at the end
 of this period, it becomes the LastKnownGood. Note that if Spec.ConfigSource is
 reset to nil (use local defaults), the LastKnownGood is also immediately reset to nil,
 because the local default config is always assumed good.
 You should not make assumptions about the node's method of determining config stability
 and correctness, as this may change or become configurable in the future.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource lastKnownGood = 3;
      Specified by:
      getLastKnownGood in interface V1.NodeConfigStatusOrBuilder

    • setLastKnownGood

      public V1.NodeConfigStatus.Builder setLastKnownGood(V1.NodeConfigSource value)
       LastKnownGood reports the checkpointed config the node will fall back to
 when it encounters an error attempting to use the Assigned config.
 The Assigned config becomes the LastKnownGood config when the node determines
 that the Assigned config is stable and correct.
 This is currently implemented as a 10-minute soak period starting when the local
 record of Assigned config is updated. If the Assigned config is Active at the end
 of this period, it becomes the LastKnownGood. Note that if Spec.ConfigSource is
 reset to nil (use local defaults), the LastKnownGood is also immediately reset to nil,
 because the local default config is always assumed good.
 You should not make assumptions about the node's method of determining config stability
 and correctness, as this may change or become configurable in the future.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource lastKnownGood = 3;

    • setLastKnownGood

      public V1.NodeConfigStatus.Builder setLastKnownGood(V1.NodeConfigSource.Builder builderForValue)
       LastKnownGood reports the checkpointed config the node will fall back to
 when it encounters an error attempting to use the Assigned config.
 The Assigned config becomes the LastKnownGood config when the node determines
 that the Assigned config is stable and correct.
 This is currently implemented as a 10-minute soak period starting when the local
 record of Assigned config is updated. If the Assigned config is Active at the end
 of this period, it becomes the LastKnownGood. Note that if Spec.ConfigSource is
 reset to nil (use local defaults), the LastKnownGood is also immediately reset to nil,
 because the local default config is always assumed good.
 You should not make assumptions about the node's method of determining config stability
 and correctness, as this may change or become configurable in the future.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource lastKnownGood = 3;

    • mergeLastKnownGood

      public V1.NodeConfigStatus.Builder mergeLastKnownGood(V1.NodeConfigSource value)
       LastKnownGood reports the checkpointed config the node will fall back to
 when it encounters an error attempting to use the Assigned config.
 The Assigned config becomes the LastKnownGood config when the node determines
 that the Assigned config is stable and correct.
 This is currently implemented as a 10-minute soak period starting when the local
 record of Assigned config is updated. If the Assigned config is Active at the end
 of this period, it becomes the LastKnownGood. Note that if Spec.ConfigSource is
 reset to nil (use local defaults), the LastKnownGood is also immediately reset to nil,
 because the local default config is always assumed good.
 You should not make assumptions about the node's method of determining config stability
 and correctness, as this may change or become configurable in the future.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource lastKnownGood = 3;

    • clearLastKnownGood

      public V1.NodeConfigStatus.Builder clearLastKnownGood()
       LastKnownGood reports the checkpointed config the node will fall back to
 when it encounters an error attempting to use the Assigned config.
 The Assigned config becomes the LastKnownGood config when the node determines
 that the Assigned config is stable and correct.
 This is currently implemented as a 10-minute soak period starting when the local
 record of Assigned config is updated. If the Assigned config is Active at the end
 of this period, it becomes the LastKnownGood. Note that if Spec.ConfigSource is
 reset to nil (use local defaults), the LastKnownGood is also immediately reset to nil,
 because the local default config is always assumed good.
 You should not make assumptions about the node's method of determining config stability
 and correctness, as this may change or become configurable in the future.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource lastKnownGood = 3;

    • getLastKnownGoodBuilder

      public V1.NodeConfigSource.Builder getLastKnownGoodBuilder()
       LastKnownGood reports the checkpointed config the node will fall back to
 when it encounters an error attempting to use the Assigned config.
 The Assigned config becomes the LastKnownGood config when the node determines
 that the Assigned config is stable and correct.
 This is currently implemented as a 10-minute soak period starting when the local
 record of Assigned config is updated. If the Assigned config is Active at the end
 of this period, it becomes the LastKnownGood. Note that if Spec.ConfigSource is
 reset to nil (use local defaults), the LastKnownGood is also immediately reset to nil,
 because the local default config is always assumed good.
 You should not make assumptions about the node's method of determining config stability
 and correctness, as this may change or become configurable in the future.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource lastKnownGood = 3;

    • getLastKnownGoodOrBuilder

      public V1.NodeConfigSourceOrBuilder getLastKnownGoodOrBuilder()
       LastKnownGood reports the checkpointed config the node will fall back to
 when it encounters an error attempting to use the Assigned config.
 The Assigned config becomes the LastKnownGood config when the node determines
 that the Assigned config is stable and correct.
 This is currently implemented as a 10-minute soak period starting when the local
 record of Assigned config is updated. If the Assigned config is Active at the end
 of this period, it becomes the LastKnownGood. Note that if Spec.ConfigSource is
 reset to nil (use local defaults), the LastKnownGood is also immediately reset to nil,
 because the local default config is always assumed good.
 You should not make assumptions about the node's method of determining config stability
 and correctness, as this may change or become configurable in the future.
 +optional
      optional .k8s.io.api.core.v1.NodeConfigSource lastKnownGood = 3;
      Specified by:
      getLastKnownGoodOrBuilder in interface V1.NodeConfigStatusOrBuilder

    • hasError

      public boolean hasError()
       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
      optional string error = 4;
      Specified by:
      hasError in interface V1.NodeConfigStatusOrBuilder

    • getError

      public String getError()
       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
      optional string error = 4;
      Specified by:
      getError in interface V1.NodeConfigStatusOrBuilder

    • getErrorBytes

      public com.google.protobuf.ByteString getErrorBytes()
       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
      optional string error = 4;
      Specified by:
      getErrorBytes in interface V1.NodeConfigStatusOrBuilder

    • setError

      public V1.NodeConfigStatus.Builder setError(String value)
       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
      optional string error = 4;

    • clearError

      public V1.NodeConfigStatus.Builder clearError()
       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
      optional string error = 4;

    • setErrorBytes

      public V1.NodeConfigStatus.Builder setErrorBytes(com.google.protobuf.ByteString value)
       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
      optional string error = 4;

    • setUnknownFields

      public final V1.NodeConfigStatus.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      Specified by:
      setUnknownFields in interface com.google.protobuf.Message.Builder
      Overrides:
      setUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<V1.NodeConfigStatus.Builder>

    • mergeUnknownFields

      public final V1.NodeConfigStatus.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      Specified by:
      mergeUnknownFields in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<V1.NodeConfigStatus.Builder>