apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:41:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-7-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-7.ec2.internal
      uid: d5296e9f-46a9-469b-bc7a-ba94910f8f9d
    resourceVersion: "15359"
    uid: 04b36067-e404-4f1a-b3b6-216fbae287b2
  spec:
    sourcePod: network-check-source-685456655f-mr8hn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:48:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.202906ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:14Z"
    - latency: 896.03µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:14Z"
    - latency: 880.025µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:14Z"
    - latency: 924.967µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:14Z"
    - latency: 963.373µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:44:14Z"
    - latency: 964.609µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:43:14Z"
    - latency: 944.644µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:42:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:41:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-7-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-7.ec2.internal
      uid: d5296e9f-46a9-469b-bc7a-ba94910f8f9d
    resourceVersion: "14889"
    uid: a99fc60c-e194-4d6b-9ef8-4227e09aec1a
  spec:
    sourcePod: network-check-source-685456655f-mr8hn
    targetEndpoint: aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:47:14Z"
      message: 'load-balancer-api-external: tcp connection to aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.268369ms
      message: 'load-balancer-api-external: tcp connection to aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:14Z"
    - latency: 6.559786ms
      message: 'load-balancer-api-external: resolved host name aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:47:14Z"
    - latency: 5.042149ms
      message: 'load-balancer-api-external: tcp connection to aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:14Z"
    - latency: 7.248272ms
      message: 'load-balancer-api-external: resolved host name aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:46:14Z"
    - latency: 3.989808ms
      message: 'load-balancer-api-external: tcp connection to aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:14Z"
    - latency: 6.19327ms
      message: 'load-balancer-api-external: resolved host name aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:45:14Z"
    - latency: 4.556607ms
      message: 'load-balancer-api-external: tcp connection to aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:44:14Z"
    - latency: 6.67674ms
      message: 'load-balancer-api-external: resolved host name aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:44:14Z"
    - latency: 4.951939ms
      message: 'load-balancer-api-external: tcp connection to aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:43:14Z"
    - latency: 6.099175ms
      message: 'load-balancer-api-external: resolved host name aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:43:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:41:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-7-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-7.ec2.internal
      uid: d5296e9f-46a9-469b-bc7a-ba94910f8f9d
    resourceVersion: "14888"
    uid: bf818609-b0d2-48c0-8e71-ce9b51521bf9
  spec:
    sourcePod: network-check-source-685456655f-mr8hn
    targetEndpoint: aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:47:14Z"
      message: 'load-balancer-api-internal: tcp connection to aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.407438ms
      message: 'load-balancer-api-internal: tcp connection to aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:14Z"
    - latency: 6.624357ms
      message: 'load-balancer-api-internal: resolved host name aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:47:14Z"
    - latency: 5.029994ms
      message: 'load-balancer-api-internal: tcp connection to aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:14Z"
    - latency: 7.288493ms
      message: 'load-balancer-api-internal: resolved host name aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:46:14Z"
    - latency: 4.530481ms
      message: 'load-balancer-api-internal: tcp connection to aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:14Z"
    - latency: 6.232431ms
      message: 'load-balancer-api-internal: resolved host name aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:45:14Z"
    - latency: 4.07985ms
      message: 'load-balancer-api-internal: tcp connection to aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:44:14Z"
    - latency: 6.701129ms
      message: 'load-balancer-api-internal: resolved host name aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:44:14Z"
    - latency: 4.888829ms
      message: 'load-balancer-api-internal: tcp connection to aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:43:14Z"
    - latency: 6.108845ms
      message: 'load-balancer-api-internal: resolved host name aaa846c10781c4f4aaa251ff1ea30a6d-ab520e233f77696a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:43:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:41:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-7-to-network-check-target-ip-10-0-128-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-7.ec2.internal
      uid: d5296e9f-46a9-469b-bc7a-ba94910f8f9d
    resourceVersion: "15356"
    uid: 85b044f7-fa73-4f3c-8c83-15cc78b495d3
  spec:
    sourcePod: network-check-source-685456655f-mr8hn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:48:14Z"
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.583321ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:14Z"
    - latency: 2.107377ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:14Z"
    - latency: 2.612743ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:14Z"
    - latency: 1.992439ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:14Z"
    - latency: 2.324837ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:44:14Z"
    - latency: 2.267167ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:43:14Z"
    - latency: 2.73015ms
      message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:42:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:41:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-7-to-network-check-target-ip-10-0-128-243
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-7.ec2.internal
      uid: d5296e9f-46a9-469b-bc7a-ba94910f8f9d
    resourceVersion: "15358"
    uid: 5d855f89-27bb-4fde-94f9-4101991f11ce
  spec:
    sourcePod: network-check-source-685456655f-mr8hn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:48:14Z"
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.940626ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:14Z"
    - latency: 2.294288ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:14Z"
    - latency: 2.256285ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:14Z"
    - latency: 2.188297ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:14Z"
    - latency: 2.494428ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:44:14Z"
    - latency: 2.023342ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:43:14Z"
    - latency: 2.599105ms
      message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:42:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:41:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-7-to-network-check-target-ip-10-0-129-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-7.ec2.internal
      uid: d5296e9f-46a9-469b-bc7a-ba94910f8f9d
    resourceVersion: "15357"
    uid: 766a91bc-0505-44be-bbd1-5b2f336c436c
  spec:
    sourcePod: network-check-source-685456655f-mr8hn
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:48:14Z"
      message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.738689ms
      message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:14Z"
    - latency: 928.488µs
      message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:14Z"
    - latency: 925.567µs
      message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:14Z"
    - latency: 1.052564ms
      message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:14Z"
    - latency: 990.707µs
      message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:44:14Z"
    - latency: 1.013809ms
      message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:43:14Z"
    - latency: 1.604553ms
      message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:42:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:41:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-7-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-7.ec2.internal
      uid: d5296e9f-46a9-469b-bc7a-ba94910f8f9d
    resourceVersion: "14887"
    uid: 63d09983-6191-4254-904b-f8bcd711f68d
  spec:
    sourcePod: network-check-source-685456655f-mr8hn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:47:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 858.724µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:14Z"
    - latency: 1.705392ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:47:14Z"
    - latency: 1.142749ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:14Z"
    - latency: 1.765645ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:46:14Z"
    - latency: 914.853µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:14Z"
    - latency: 1.722622ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:45:14Z"
    - latency: 1.095429ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:44:14Z"
    - latency: 1.695101ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:44:14Z"
    - latency: 968.541µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:43:14Z"
    - latency: 1.909912ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:43:14Z"
kind: List
metadata:
  resourceVersion: ""