apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T04:31:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-39-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-39.ec2.internal
      uid: 7b3358ca-b5ef-4656-9132-a80fc8914eb4
    resourceVersion: "22665"
    uid: 6cc17821-ffd3-445f-a6eb-7a0255dcd5ef
  spec:
    sourcePod: network-check-source-685456655f-hpkqq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:38:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.066431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:38:05Z"
    - latency: 904.67µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:37:05Z"
    - latency: 824.568µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:36:05Z"
    - latency: 997.14µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:35:05Z"
    - latency: 909µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:34:05Z"
    - latency: 974.674µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:33:05Z"
    - latency: 1.04872ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:32:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T04:31:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-39-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-39.ec2.internal
      uid: 7b3358ca-b5ef-4656-9132-a80fc8914eb4
    resourceVersion: "21449"
    uid: a11b604d-47a7-4b48-ae59-e5685b6b5e19
  spec:
    sourcePod: network-check-source-685456655f-hpkqq
    targetEndpoint: a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:37:05Z"
      message: 'load-balancer-api-external: tcp connection to a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.938536ms
      message: 'load-balancer-api-external: tcp connection to a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:37:05Z"
    - latency: 15.819626ms
      message: 'load-balancer-api-external: resolved host name a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:37:05Z"
    - latency: 3.696049ms
      message: 'load-balancer-api-external: tcp connection to a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:36:05Z"
    - latency: 8.780824ms
      message: 'load-balancer-api-external: resolved host name a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:36:05Z"
    - latency: 4.63852ms
      message: 'load-balancer-api-external: tcp connection to a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:35:05Z"
    - latency: 9.546433ms
      message: 'load-balancer-api-external: resolved host name a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:35:05Z"
    - latency: 4.70661ms
      message: 'load-balancer-api-external: tcp connection to a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:34:05Z"
    - latency: 9.366232ms
      message: 'load-balancer-api-external: resolved host name a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:34:05Z"
    - latency: 5.013862ms
      message: 'load-balancer-api-external: tcp connection to a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:33:05Z"
    - latency: 8.504153ms
      message: 'load-balancer-api-external: resolved host name a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:33:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T04:31:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-39-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-39.ec2.internal
      uid: 7b3358ca-b5ef-4656-9132-a80fc8914eb4
    resourceVersion: "21448"
    uid: d2f4b9b7-d25b-406e-8e2b-fad9f332f000
  spec:
    sourcePod: network-check-source-685456655f-hpkqq
    targetEndpoint: a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:37:05Z"
      message: 'load-balancer-api-internal: tcp connection to a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.522556ms
      message: 'load-balancer-api-internal: tcp connection to a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:37:05Z"
    - latency: 15.534809ms
      message: 'load-balancer-api-internal: resolved host name a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:37:05Z"
    - latency: 5.972341ms
      message: 'load-balancer-api-internal: tcp connection to a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:36:05Z"
    - latency: 8.858272ms
      message: 'load-balancer-api-internal: resolved host name a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:36:05Z"
    - latency: 5.548054ms
      message: 'load-balancer-api-internal: tcp connection to a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:35:05Z"
    - latency: 9.495677ms
      message: 'load-balancer-api-internal: resolved host name a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:35:05Z"
    - latency: 4.695805ms
      message: 'load-balancer-api-internal: tcp connection to a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:34:05Z"
    - latency: 9.4298ms
      message: 'load-balancer-api-internal: resolved host name a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:34:05Z"
    - latency: 4.968769ms
      message: 'load-balancer-api-internal: tcp connection to a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:33:05Z"
    - latency: 8.568623ms
      message: 'load-balancer-api-internal: resolved host name a4d6a648de8474c28ad0a1d7f9725a54-c28cb498e9b63742.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:33:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T04:31:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-39-to-network-check-target-ip-10-0-129-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-39.ec2.internal
      uid: 7b3358ca-b5ef-4656-9132-a80fc8914eb4
    resourceVersion: "22662"
    uid: 51f85c38-9ff1-404b-915b-68e898ecea4d
  spec:
    sourcePod: network-check-source-685456655f-hpkqq
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:38:05Z"
      message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.017275ms
      message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:38:05Z"
    - latency: 779.375µs
      message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:37:05Z"
    - latency: 1.190162ms
      message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:36:05Z"
    - latency: 780.312µs
      message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:35:05Z"
    - latency: 1.299289ms
      message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:34:05Z"
    - latency: 870.799µs
      message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:33:05Z"
    - latency: 1.665384ms
      message: 'network-check-target-ip-10-0-129-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:32:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T04:31:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-39-to-network-check-target-ip-10-0-137-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-39.ec2.internal
      uid: 7b3358ca-b5ef-4656-9132-a80fc8914eb4
    resourceVersion: "22663"
    uid: 59bc903b-d8a3-4582-a3e6-6dd19985b0ff
  spec:
    sourcePod: network-check-source-685456655f-hpkqq
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:38:05Z"
      message: 'network-check-target-ip-10-0-137-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.407506ms
      message: 'network-check-target-ip-10-0-137-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:38:05Z"
    - latency: 2.256116ms
      message: 'network-check-target-ip-10-0-137-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:37:05Z"
    - latency: 2.041175ms
      message: 'network-check-target-ip-10-0-137-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:36:05Z"
    - latency: 2.486469ms
      message: 'network-check-target-ip-10-0-137-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:35:05Z"
    - latency: 5.534095ms
      message: 'network-check-target-ip-10-0-137-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:34:05Z"
    - latency: 2.22651ms
      message: 'network-check-target-ip-10-0-137-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:33:05Z"
    - latency: 2.240775ms
      message: 'network-check-target-ip-10-0-137-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:32:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T04:31:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-39-to-network-check-target-ip-10-0-140-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-39.ec2.internal
      uid: 7b3358ca-b5ef-4656-9132-a80fc8914eb4
    resourceVersion: "22664"
    uid: ec9b8b84-4699-4ac5-98ff-dc8d30a6c293
  spec:
    sourcePod: network-check-source-685456655f-hpkqq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:38:05Z"
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.422997ms
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:38:05Z"
    - latency: 2.400913ms
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:37:05Z"
    - latency: 1.835742ms
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:36:05Z"
    - latency: 2.357728ms
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:35:05Z"
    - latency: 2.172479ms
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:34:05Z"
    - latency: 1.840166ms
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:33:05Z"
    - latency: 2.73133ms
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:32:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T04:31:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-39-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-39.ec2.internal
      uid: 7b3358ca-b5ef-4656-9132-a80fc8914eb4
    resourceVersion: "21447"
    uid: b6aef147-64bb-4b1e-97aa-6a987d51a502
  spec:
    sourcePod: network-check-source-685456655f-hpkqq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T04:37:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.281541ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:37:05Z"
    - latency: 2.129593ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:37:05Z"
    - latency: 994.506µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:36:05Z"
    - latency: 1.842009ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:36:05Z"
    - latency: 1.053241ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:35:05Z"
    - latency: 2.164631ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:35:05Z"
    - latency: 3.95558ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:34:05Z"
    - latency: 1.87183ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:34:05Z"
    - latency: 981.24µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T04:33:05Z"
    - latency: 1.753979ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T04:33:05Z"
kind: List
metadata:
  resourceVersion: ""