PodNetworkConnectivityCheck Compatibility level 4: No compatibility is provided, the api can change at any point for any reason. These capabilities should not be used by applications needing long term support.
PodNetworkConnectivityCheck Compatibility level 4: No compatibility is provided, the api can change at any point for any reason. These capabilities should not be used by applications needing long term support.
object
spec
Property | Type | Description |
---|---|---|
|
|
apiVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources |
|
|
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds |
|
Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata |
|
|
|
Spec defines the source and target of the connectivity check |
|
|
Status contains the observed status of the connectivity check |
Spec defines the source and target of the connectivity check
object
sourcePod
targetEndpoint
Property | Type | Description |
---|---|---|
|
|
SourcePod names the pod from which the condition will be checked |
|
|
EndpointAddress to check. A TCP address of the form host:port. Note that if host is a DNS name, then the check would fail if the DNS name cannot be resolved. Specify an IP address for host to bypass DNS name lookup. |
|
|
TLSClientCert, if specified, references a kubernetes.io/tls type secret with 'tls.crt' and 'tls.key' entries containing an optional TLS client certificate and key to be used when checking endpoints that require a client certificate in order to gracefully preform the scan without causing excessive logging in the endpoint process. The secret must exist in the same namespace as this resource. |
TLSClientCert, if specified, references a kubernetes.io/tls type secret with 'tls.crt' and 'tls.key' entries containing an optional TLS client certificate and key to be used when checking endpoints that require a client certificate in order to gracefully preform the scan without causing excessive logging in the endpoint process. The secret must exist in the same namespace as this resource.
object
name
Property | Type | Description |
---|---|---|
|
|
name is the metadata.name of the referenced secret |
Status contains the observed status of the connectivity check
object
Property | Type | Description |
---|---|---|
|
|
Conditions summarize the status of the check |
|
|
PodNetworkConnectivityCheckCondition represents the overall status of the pod network connectivity. |
|
|
Failures contains logs of unsuccessful check actions |
|
|
LogEntry records events |
|
|
Outages contains logs of time periods of outages |
|
|
OutageEntry records time period of an outage |
|
|
Successes contains logs successful check actions |
|
|
LogEntry records events |
PodNetworkConnectivityCheckCondition represents the overall status of the pod network connectivity.
object
status
type
Property | Type | Description |
---|---|---|
|
`` |
Last time the condition transitioned from one status to another. |
|
|
Message indicating details about last transition in a human readable format. |
|
|
Reason for the condition’s last status transition in a machine readable format. |
|
|
Status of the condition |
|
|
Type of the condition |
LogEntry records events
object
success
Property | Type | Description |
---|---|---|
|
`` |
Latency records how long the action mentioned in the entry took. |
|
|
Message explaining status in a human readable format. |
|
|
Reason for status in a machine readable format. |
|
|
Success indicates if the log entry indicates a success or failure. |
|
`` |
Start time of check action. |
OutageEntry records time period of an outage
object
Property | Type | Description |
---|---|---|
|
`` |
End of outage detected |
|
|
EndLogs contains log entries related to the end of this outage. Should contain the success entry that resolved the outage and possibly a few of the failure log entries that preceded it. |
|
|
LogEntry records events |
|
|
Message summarizes outage details in a human readable format. |
|
`` |
Start of outage detected |
|
|
StartLogs contains log entries related to the start of this outage. Should contain the original failure, any entries where the failure mode changed. |
|
|
LogEntry records events |
EndLogs contains log entries related to the end of this outage. Should contain the success entry that resolved the outage and possibly a few of the failure log entries that preceded it.
array
LogEntry records events
object
success
Property | Type | Description |
---|---|---|
|
`` |
Latency records how long the action mentioned in the entry took. |
|
|
Message explaining status in a human readable format. |
|
|
Reason for status in a machine readable format. |
|
|
Success indicates if the log entry indicates a success or failure. |
|
`` |
Start time of check action. |
StartLogs contains log entries related to the start of this outage. Should contain the original failure, any entries where the failure mode changed.
array
LogEntry records events
object
success
Property | Type | Description |
---|---|---|
|
`` |
Latency records how long the action mentioned in the entry took. |
|
|
Message explaining status in a human readable format. |
|
|
Reason for status in a machine readable format. |
|
|
Success indicates if the log entry indicates a success or failure. |
|
`` |
Start time of check action. |
LogEntry records events
object
success
Property | Type | Description |
---|---|---|
|
`` |
Latency records how long the action mentioned in the entry took. |
|
|
Message explaining status in a human readable format. |
|
|
Reason for status in a machine readable format. |
|
|
Success indicates if the log entry indicates a success or failure. |
|
`` |
Start time of check action. |
The following api endpoints are available:
/apis/controlplane.operator.openshift.io/v1alpha1/podnetworkconnectivitychecks
GET
: list objects of kind PodNetworkConnectivityCheck
/apis/controlplane.operator.openshift.io/v1alpha1/namespaces/{namespace}/podnetworkconnectivitychecks
DELETE
: delete collection of PodNetworkConnectivityCheck
GET
: list objects of kind PodNetworkConnectivityCheck
POST
: create a PodNetworkConnectivityCheck
/apis/controlplane.operator.openshift.io/v1alpha1/namespaces/{namespace}/podnetworkconnectivitychecks/{name}
DELETE
: delete a PodNetworkConnectivityCheck
GET
: read the specified PodNetworkConnectivityCheck
PATCH
: partially update the specified PodNetworkConnectivityCheck
PUT
: replace the specified PodNetworkConnectivityCheck
/apis/controlplane.operator.openshift.io/v1alpha1/namespaces/{namespace}/podnetworkconnectivitychecks/{name}/status
GET
: read status of the specified PodNetworkConnectivityCheck
PATCH
: partially update status of the specified PodNetworkConnectivityCheck
PUT
: replace status of the specified PodNetworkConnectivityCheck
GET
list objects of kind PodNetworkConnectivityCheck
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
Empty |
DELETE
delete collection of PodNetworkConnectivityCheck
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
Empty |
GET
list objects of kind PodNetworkConnectivityCheck
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
Empty |
POST
create a PodNetworkConnectivityCheck
Parameter | Type | Description |
---|---|---|
|
|
When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
|
fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized |
Empty |
Parameter | Type | Description |
---|---|---|
|
|
name of the PodNetworkConnectivityCheck |
DELETE
delete a PodNetworkConnectivityCheck
Parameter | Type | Description |
---|---|---|
|
|
When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
HTTP code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized |
Empty |
GET
read the specified PodNetworkConnectivityCheck
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
Empty |
PATCH
partially update the specified PodNetworkConnectivityCheck
Parameter | Type | Description |
---|---|---|
|
|
When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
|
fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
Empty |
PUT
replace the specified PodNetworkConnectivityCheck
Parameter | Type | Description |
---|---|---|
|
|
When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
|
fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized |
Empty |
Parameter | Type | Description |
---|---|---|
|
|
name of the PodNetworkConnectivityCheck |
GET
read status of the specified PodNetworkConnectivityCheck
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
Empty |
PATCH
partially update status of the specified PodNetworkConnectivityCheck
Parameter | Type | Description |
---|---|---|
|
|
When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
|
fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
Empty |
PUT
replace status of the specified PodNetworkConnectivityCheck
Parameter | Type | Description |
---|---|---|
|
|
When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
|
fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized |
Empty |