apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T00:36:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-174-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-174.us-west-1.compute.internal
      uid: ab701823-7efb-48ac-9740-9b79c58b6b57
    resourceVersion: "17936"
    uid: eb56e33f-16bb-4a7a-9ca0-25c2f6f7792e
  spec:
    sourcePod: network-check-source-6f78d59f99-rrkqz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T00:43:22Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.170715ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:43:22Z"
    - latency: 1.058306ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:42:22Z"
    - latency: 1.438678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:41:22Z"
    - latency: 1.049413ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:40:22Z"
    - latency: 948.965µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:39:22Z"
    - latency: 860.942µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:38:22Z"
    - latency: 1.324144ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:37:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T00:36:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-174-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-174.us-west-1.compute.internal
      uid: ab701823-7efb-48ac-9740-9b79c58b6b57
    resourceVersion: "22332"
    uid: cc839c06-bceb-41c2-9d93-9c18c6d0948b
  spec:
    sourcePod: network-check-source-6f78d59f99-rrkqz
    targetEndpoint: a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T00:42:22Z"
      message: 'load-balancer-api-external: tcp connection to a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 52.80425ms
      message: 'load-balancer-api-external: tcp connection to a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:48:22Z"
    - latency: 8.156703ms
      message: 'load-balancer-api-external: resolved host name a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T00:48:22Z"
    - latency: 52.690918ms
      message: 'load-balancer-api-external: tcp connection to a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:47:22Z"
    - latency: 6.17638ms
      message: 'load-balancer-api-external: resolved host name a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T00:47:22Z"
    - latency: 54.055256ms
      message: 'load-balancer-api-external: tcp connection to a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:46:22Z"
    - latency: 5.727995ms
      message: 'load-balancer-api-external: resolved host name a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T00:46:22Z"
    - latency: 53.800085ms
      message: 'load-balancer-api-external: tcp connection to a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:45:22Z"
    - latency: 8.079438ms
      message: 'load-balancer-api-external: resolved host name a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T00:45:22Z"
    - latency: 51.872669ms
      message: 'load-balancer-api-external: tcp connection to a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:44:22Z"
    - latency: 6.393869ms
      message: 'load-balancer-api-external: resolved host name a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T00:44:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T00:36:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-174-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-174.us-west-1.compute.internal
      uid: ab701823-7efb-48ac-9740-9b79c58b6b57
    resourceVersion: "22331"
    uid: 577c29e7-81c0-4e74-9c70-5b7d2b6f33f1
  spec:
    sourcePod: network-check-source-6f78d59f99-rrkqz
    targetEndpoint: a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T00:42:22Z"
      message: 'load-balancer-api-internal: tcp connection to a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 52.811836ms
      message: 'load-balancer-api-internal: tcp connection to a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:48:22Z"
    - latency: 8.209237ms
      message: 'load-balancer-api-internal: resolved host name a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T00:48:22Z"
    - latency: 53.14247ms
      message: 'load-balancer-api-internal: tcp connection to a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:47:22Z"
    - latency: 6.166467ms
      message: 'load-balancer-api-internal: resolved host name a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T00:47:22Z"
    - latency: 54.014138ms
      message: 'load-balancer-api-internal: tcp connection to a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:46:22Z"
    - latency: 5.686049ms
      message: 'load-balancer-api-internal: resolved host name a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T00:46:22Z"
    - latency: 53.790878ms
      message: 'load-balancer-api-internal: tcp connection to a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:45:22Z"
    - latency: 8.00382ms
      message: 'load-balancer-api-internal: resolved host name a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T00:45:22Z"
    - latency: 52.643212ms
      message: 'load-balancer-api-internal: tcp connection to a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:44:22Z"
    - latency: 6.390834ms
      message: 'load-balancer-api-internal: resolved host name a6d496743d9e84c5981c8445c7f0f745-7fd7323c08f9c5f9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T00:44:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T00:36:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-174-to-network-check-target-ip-10-0-134-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-174.us-west-1.compute.internal
      uid: ab701823-7efb-48ac-9740-9b79c58b6b57
    resourceVersion: "17931"
    uid: 263e647c-1023-4e33-b0f9-71ff71bcf32a
  spec:
    sourcePod: network-check-source-6f78d59f99-rrkqz
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T00:43:22Z"
      message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.071664ms
      message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:43:22Z"
    - latency: 1.852901ms
      message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:42:22Z"
    - latency: 1.917557ms
      message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:41:22Z"
    - latency: 1.688214ms
      message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:40:22Z"
    - latency: 1.580449ms
      message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:39:22Z"
    - latency: 1.610379ms
      message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:38:22Z"
    - latency: 1.930317ms
      message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:37:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T00:36:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-174-to-network-check-target-ip-10-0-136-69
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-174.us-west-1.compute.internal
      uid: ab701823-7efb-48ac-9740-9b79c58b6b57
    resourceVersion: "17930"
    uid: 018f1083-20f5-4053-be88-09a932de1696
  spec:
    sourcePod: network-check-source-6f78d59f99-rrkqz
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T00:43:22Z"
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.215411ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:43:22Z"
    - latency: 2.07462ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:42:22Z"
    - latency: 2.059608ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:41:22Z"
    - latency: 2.142576ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:40:22Z"
    - latency: 1.915111ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:39:22Z"
    - latency: 2.067217ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:38:22Z"
    - latency: 2.278241ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:37:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T00:36:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-174-to-network-check-target-ip-10-0-139-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-174.us-west-1.compute.internal
      uid: ab701823-7efb-48ac-9740-9b79c58b6b57
    resourceVersion: "17939"
    uid: afb4c48f-1a5d-4ea1-a5e6-ba343e200d0e
  spec:
    sourcePod: network-check-source-6f78d59f99-rrkqz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T00:43:23Z"
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 825.281µs
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:43:23Z"
    - latency: 1.109989ms
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:42:23Z"
    - latency: 1.024874ms
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:41:23Z"
    - latency: 1.107544ms
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:40:23Z"
    - latency: 634.822µs
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:39:23Z"
    - latency: 1.08372ms
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:38:23Z"
    - latency: 1.323692ms
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:37:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T00:36:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-174-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-174.us-west-1.compute.internal
      uid: ab701823-7efb-48ac-9740-9b79c58b6b57
    resourceVersion: "22335"
    uid: 96503fb8-edde-44fe-be58-2a4914a10437
  spec:
    sourcePod: network-check-source-6f78d59f99-rrkqz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T00:42:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 927.967µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:48:22Z"
    - latency: 779.268µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T00:48:22Z"
    - latency: 1.196048ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:47:22Z"
    - latency: 980.872µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T00:47:22Z"
    - latency: 1.043465ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:46:22Z"
    - latency: 653.972µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T00:46:22Z"
    - latency: 878.579µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:45:22Z"
    - latency: 776.25µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T00:45:22Z"
    - latency: 844.061µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T00:44:22Z"
    - latency: 673.795µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T00:44:22Z"
kind: List
metadata:
  resourceVersion: ""