apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T17:36:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-129-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-129.ec2.internal
      uid: 23bdddef-b2d7-45bf-a264-ac3eddc107ba
    resourceVersion: "23825"
    uid: 7aa7dcbb-417d-49a4-9a5a-7137676893cf
  spec:
    sourcePod: network-check-source-6f8b768455-zpd5r
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T17:43:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 969.688µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:43:37Z"
    - latency: 916.038µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:42:37Z"
    - latency: 878.231µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:41:37Z"
    - latency: 944.614µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:40:37Z"
    - latency: 2.240699ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:39:37Z"
    - latency: 974.878µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:38:37Z"
    - latency: 1.060268ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:37:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T17:36:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-129-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-129.ec2.internal
      uid: 23bdddef-b2d7-45bf-a264-ac3eddc107ba
    resourceVersion: "22690"
    uid: 32944bb2-15fc-403a-a78e-b6ee604f0439
  spec:
    sourcePod: network-check-source-6f8b768455-zpd5r
    targetEndpoint: a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T17:42:37Z"
      message: 'load-balancer-api-external: tcp connection to a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.615736ms
      message: 'load-balancer-api-external: tcp connection to a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:42:37Z"
    - latency: 7.845048ms
      message: 'load-balancer-api-external: resolved host name a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:42:37Z"
    - latency: 4.150698ms
      message: 'load-balancer-api-external: tcp connection to a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:41:37Z"
    - latency: 8.493787ms
      message: 'load-balancer-api-external: resolved host name a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:41:37Z"
    - latency: 4.233936ms
      message: 'load-balancer-api-external: tcp connection to a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:40:37Z"
    - latency: 8.01279ms
      message: 'load-balancer-api-external: resolved host name a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:40:37Z"
    - latency: 4.596156ms
      message: 'load-balancer-api-external: tcp connection to a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:39:37Z"
    - latency: 12.547002ms
      message: 'load-balancer-api-external: resolved host name a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:39:37Z"
    - latency: 4.606491ms
      message: 'load-balancer-api-external: tcp connection to a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:38:37Z"
    - latency: 9.007297ms
      message: 'load-balancer-api-external: resolved host name a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:38:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T17:36:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-129-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-129.ec2.internal
      uid: 23bdddef-b2d7-45bf-a264-ac3eddc107ba
    resourceVersion: "22689"
    uid: 60ba6f2b-58f8-407f-8ba4-788c700a3942
  spec:
    sourcePod: network-check-source-6f8b768455-zpd5r
    targetEndpoint: a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T17:42:37Z"
      message: 'load-balancer-api-internal: tcp connection to a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.595127ms
      message: 'load-balancer-api-internal: tcp connection to a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:42:37Z"
    - latency: 7.933023ms
      message: 'load-balancer-api-internal: resolved host name a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:42:37Z"
    - latency: 4.137407ms
      message: 'load-balancer-api-internal: tcp connection to a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:41:37Z"
    - latency: 8.548311ms
      message: 'load-balancer-api-internal: resolved host name a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:41:37Z"
    - latency: 4.436579ms
      message: 'load-balancer-api-internal: tcp connection to a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:40:37Z"
    - latency: 8.058334ms
      message: 'load-balancer-api-internal: resolved host name a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:40:37Z"
    - latency: 4.558318ms
      message: 'load-balancer-api-internal: tcp connection to a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:39:37Z"
    - latency: 12.723855ms
      message: 'load-balancer-api-internal: resolved host name a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:39:37Z"
    - latency: 3.939805ms
      message: 'load-balancer-api-internal: tcp connection to a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:38:37Z"
    - latency: 9.044911ms
      message: 'load-balancer-api-internal: resolved host name a7b01bc5f1807423192b24ba876a861a-3bff1f1bee11ec4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:38:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T17:36:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-129-to-network-check-target-ip-10-0-128-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-129.ec2.internal
      uid: 23bdddef-b2d7-45bf-a264-ac3eddc107ba
    resourceVersion: "23822"
    uid: 2d38dfe5-9f1c-4d42-8167-c9f10e7567e1
  spec:
    sourcePod: network-check-source-6f8b768455-zpd5r
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T17:43:37Z"
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 903.692µs
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:43:37Z"
    - latency: 1.409642ms
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:42:37Z"
    - latency: 834.852µs
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:41:37Z"
    - latency: 1.573412ms
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:40:37Z"
    - latency: 820.394µs
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:39:37Z"
    - latency: 913.165µs
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:38:37Z"
    - latency: 1.750854ms
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:37:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T17:36:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-129-to-network-check-target-ip-10-0-130-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-129.ec2.internal
      uid: 23bdddef-b2d7-45bf-a264-ac3eddc107ba
    resourceVersion: "23824"
    uid: 1afb87e0-efca-4775-a323-b93014fb8dc9
  spec:
    sourcePod: network-check-source-6f8b768455-zpd5r
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T17:43:37Z"
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.088843ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:43:37Z"
    - latency: 2.111421ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:42:37Z"
    - latency: 2.227461ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:41:37Z"
    - latency: 2.716037ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:40:37Z"
    - latency: 3.931536ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:39:37Z"
    - latency: 2.251453ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:38:37Z"
    - latency: 2.724115ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:37:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T17:36:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-129-to-network-check-target-ip-10-0-143-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-129.ec2.internal
      uid: 23bdddef-b2d7-45bf-a264-ac3eddc107ba
    resourceVersion: "23823"
    uid: d1fabbdb-8065-4094-bea0-4960fad8b7e6
  spec:
    sourcePod: network-check-source-6f8b768455-zpd5r
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T17:43:37Z"
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.365959ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:43:37Z"
    - latency: 2.52382ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:42:37Z"
    - latency: 2.622632ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:41:37Z"
    - latency: 2.297137ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:40:37Z"
    - latency: 3.163589ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:39:37Z"
    - latency: 2.412975ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:38:37Z"
    - latency: 2.372582ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:37:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T17:36:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-129-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-129.ec2.internal
      uid: 23bdddef-b2d7-45bf-a264-ac3eddc107ba
    resourceVersion: "22688"
    uid: 51cabec1-8abb-4031-8e59-98c2a2c7cb01
  spec:
    sourcePod: network-check-source-6f8b768455-zpd5r
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T17:42:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 849.66µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:42:37Z"
    - latency: 1.645937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:42:37Z"
    - latency: 1.146304ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:41:37Z"
    - latency: 1.93434ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:41:37Z"
    - latency: 1.095227ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:40:37Z"
    - latency: 2.010171ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:40:37Z"
    - latency: 1.0587ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:39:37Z"
    - latency: 3.004508ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:39:37Z"
    - latency: 1.311978ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:38:37Z"
    - latency: 1.868817ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:38:37Z"
kind: List
metadata:
  resourceVersion: ""