REST Resource: namespaces.configurations

Resource: Configuration

Configuration represents the "floating HEAD" of a linear history of Revisions, and optionally how the containers those revisions reference are built. Users create new Revisions by updating the Configuration's spec. The "latest created" revision's name is available under status, as is the "latest ready" revision's name. See also: https://github.com/knative/serving/blob/master/docs/spec/overview.md#configuration

JSON representation
{
  "apiVersion": string,
  "kind": string,
  "metadata": {
    object (ObjectMeta)
  },
  "spec": {
    object (ConfigurationSpec)
  },
  "status": {
    object (ConfigurationStatus)
  }
}
Fields
apiVersion

string

The API version for this call such as "serving.knative.dev/v1alpha1".

kind

string

The kind of resource, in this case always "Configuration".

metadata

object (ObjectMeta)

Metadata associated with this Configuration, including name, namespace, labels, and annotations.

spec

object (ConfigurationSpec)

Spec holds the desired state of the Configuration (from the client).

status

object (ConfigurationStatus)

Status communicates the observed state of the Configuration (from the controller).

ConfigurationStatus

ConfigurationStatus communicates the observed state of the Configuration (from the controller).

JSON representation
{
  "latestCreatedRevisionName": string,
  "latestReadyRevisionName": string,
  "observedGeneration": number,
  "conditions": [
    {
      object (ConfigurationCondition)
    }
  ]
}
Fields
latestCreatedRevisionName

string

LatestCreatedRevisionName is the last revision that was created from this Configuration. It might not be ready yet, for that use LatestReadyRevisionName.

latestReadyRevisionName

string

LatestReadyRevisionName holds the name of the latest Revision stamped out from this Configuration that has had its "Ready" condition become "True".

observedGeneration

number

ObservedGeneration is the 'Generation' of the Configuration that was last processed by the controller. The observed generation is updated even if the controller failed to process the spec and create the Revision.

Clients polling for completed reconciliation should poll until observedGeneration = metadata.generation, and the Ready condition's status is True or False.

conditions[]

object (ConfigurationCondition)

Conditions communicates information about ongoing/complete reconciliation processes that bring the "spec" inline with the observed state of the world.

ConfigurationCondition

ConfigurationCondition defines a readiness condition for a Configuration.

JSON representation
{
  "type": string,
  "status": string,
  "reason": string,
  "message": string,
  "lastTransitionTime": string,
  "severity": string
}
Fields
type

string

ConfigurationConditionType is used to communicate the status of the reconciliation process. See also: https://github.com/knative/serving/blob/master/docs/spec/errors.md#error-conditions-and-reporting Types include:"Ready"

status

string

Status of the condition, one of True, False, Unknown.

reason

string

One-word CamelCase reason for the condition's last transition. +optional

message

string

Human-readable message indicating details about last transition. +optional

lastTransitionTime

string (Timestamp format)

Last time the condition transitioned from one status to another. +optional

A timestamp in RFC3339 UTC "Zulu" format, accurate to nanoseconds. Example: "2014-10-02T15:01:23.045123456Z".

severity

string

How to interpret failures of this condition, one of Error, Warning, Info +optional

Methods

get

Rpc to get information about a configuration.

list

Rpc to list configurations.
Kunde den här sidan hjälpa dig? Berätta:

Skicka feedback om ...