apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T04:03:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-87-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-87.ec2.internal
      uid: 7db5abe9-b4fc-4873-b2cb-fd86cac9e7cc
    resourceVersion: "22380"
    uid: 8ca722e8-275d-4a2a-83ac-412254ed9787
  spec:
    sourcePod: network-check-source-7d88cb55d8-knxzz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T04:10:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.095965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:10:04Z"
    - latency: 840.231µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:09:04Z"
    - latency: 1.0715ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:08:04Z"
    - latency: 1.130004ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:07:04Z"
    - latency: 936.926µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:06:04Z"
    - latency: 952.55µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:05:04Z"
    - latency: 1.133209ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:04:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T04:03:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-87-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-87.ec2.internal
      uid: 7db5abe9-b4fc-4873-b2cb-fd86cac9e7cc
    resourceVersion: "21158"
    uid: 0471e787-f37c-4a93-a4b8-f4ba776b25d3
  spec:
    sourcePod: network-check-source-7d88cb55d8-knxzz
    targetEndpoint: ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T04:09:04Z"
      message: 'load-balancer-api-external: tcp connection to ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.998136ms
      message: 'load-balancer-api-external: tcp connection to ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:09:04Z"
    - latency: 8.191529ms
      message: 'load-balancer-api-external: resolved host name ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:09:04Z"
    - latency: 4.514888ms
      message: 'load-balancer-api-external: tcp connection to ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:08:04Z"
    - latency: 10.783632ms
      message: 'load-balancer-api-external: resolved host name ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:08:04Z"
    - latency: 5.444058ms
      message: 'load-balancer-api-external: tcp connection to ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:07:04Z"
    - latency: 13.900553ms
      message: 'load-balancer-api-external: resolved host name ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:07:04Z"
    - latency: 4.118715ms
      message: 'load-balancer-api-external: tcp connection to ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:06:04Z"
    - latency: 8.161619ms
      message: 'load-balancer-api-external: resolved host name ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:06:04Z"
    - latency: 4.368846ms
      message: 'load-balancer-api-external: tcp connection to ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:05:04Z"
    - latency: 8.691475ms
      message: 'load-balancer-api-external: resolved host name ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:05:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T04:03:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-87-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-87.ec2.internal
      uid: 7db5abe9-b4fc-4873-b2cb-fd86cac9e7cc
    resourceVersion: "21157"
    uid: 938abb1c-fd01-422a-a572-e2e62bc90279
  spec:
    sourcePod: network-check-source-7d88cb55d8-knxzz
    targetEndpoint: ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T04:09:04Z"
      message: 'load-balancer-api-internal: tcp connection to ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.309457ms
      message: 'load-balancer-api-internal: tcp connection to ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:09:04Z"
    - latency: 8.141436ms
      message: 'load-balancer-api-internal: resolved host name ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:09:04Z"
    - latency: 4.526605ms
      message: 'load-balancer-api-internal: tcp connection to ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:08:04Z"
    - latency: 10.706308ms
      message: 'load-balancer-api-internal: resolved host name ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:08:04Z"
    - latency: 5.139884ms
      message: 'load-balancer-api-internal: tcp connection to ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:07:04Z"
    - latency: 13.849395ms
      message: 'load-balancer-api-internal: resolved host name ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:07:04Z"
    - latency: 4.235974ms
      message: 'load-balancer-api-internal: tcp connection to ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:06:04Z"
    - latency: 8.069226ms
      message: 'load-balancer-api-internal: resolved host name ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:06:04Z"
    - latency: 4.590912ms
      message: 'load-balancer-api-internal: tcp connection to ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:05:04Z"
    - latency: 9.404024ms
      message: 'load-balancer-api-internal: resolved host name ad1e827cd92514d249bde51127d1f81d-5468cde2407381d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:05:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T04:03:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-87-to-network-check-target-ip-10-0-129-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-87.ec2.internal
      uid: 7db5abe9-b4fc-4873-b2cb-fd86cac9e7cc
    resourceVersion: "22377"
    uid: ca9e8fda-fc6b-4baf-9a54-6ffd44b3e5c8
  spec:
    sourcePod: network-check-source-7d88cb55d8-knxzz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T04:10:04Z"
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.374µs
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:10:04Z"
    - latency: 1.060876ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:09:04Z"
    - latency: 1.869804ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:08:04Z"
    - latency: 1.187977ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:07:04Z"
    - latency: 879.933µs
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:06:04Z"
    - latency: 776.418µs
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:05:04Z"
    - latency: 1.858664ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:04:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T04:03:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-87-to-network-check-target-ip-10-0-134-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-87.ec2.internal
      uid: 7db5abe9-b4fc-4873-b2cb-fd86cac9e7cc
    resourceVersion: "22378"
    uid: b41fa38b-c4ef-40e6-893f-e6e47673b75c
  spec:
    sourcePod: network-check-source-7d88cb55d8-knxzz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T04:10:04Z"
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.892479ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:10:04Z"
    - latency: 1.911457ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:09:04Z"
    - latency: 2.112068ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:08:04Z"
    - latency: 2.020657ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:07:04Z"
    - latency: 1.916209ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:06:04Z"
    - latency: 2.06141ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:05:04Z"
    - latency: 2.10366ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:04:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T04:03:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-87-to-network-check-target-ip-10-0-138-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-87.ec2.internal
      uid: 7db5abe9-b4fc-4873-b2cb-fd86cac9e7cc
    resourceVersion: "22379"
    uid: c45550ca-4c06-4e01-9bf1-4461038cf852
  spec:
    sourcePod: network-check-source-7d88cb55d8-knxzz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T04:10:04Z"
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.485884ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:10:04Z"
    - latency: 2.013872ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:09:04Z"
    - latency: 2.639731ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:08:04Z"
    - latency: 2.34855ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:07:04Z"
    - latency: 2.273438ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:06:04Z"
    - latency: 2.282805ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:05:04Z"
    - latency: 2.204618ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:04:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T04:03:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-87-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-87.ec2.internal
      uid: 7db5abe9-b4fc-4873-b2cb-fd86cac9e7cc
    resourceVersion: "21155"
    uid: da59beda-7389-4db8-8c11-112d44c65026
  spec:
    sourcePod: network-check-source-7d88cb55d8-knxzz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T04:09:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.091095ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:09:04Z"
    - latency: 1.747935ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:09:04Z"
    - latency: 776.819µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:08:04Z"
    - latency: 2.065869ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:08:04Z"
    - latency: 795.897µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:07:04Z"
    - latency: 1.759543ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:07:04Z"
    - latency: 922.102µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:06:04Z"
    - latency: 1.728084ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:06:04Z"
    - latency: 1.195146ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:05:04Z"
    - latency: 2.046032ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:05:04Z"
kind: List
metadata:
  resourceVersion: ""