apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T05:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-9-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-9.ec2.internal
      uid: 0f639430-5a54-4ae9-8083-faf165506315
    resourceVersion: "23511"
    uid: 127ab5d2-e9d0-45c9-9b25-76f315f3b575
  spec:
    sourcePod: network-check-source-869dcfcdcd-d82p2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T05:10:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 889.104µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:10:27Z"
    - latency: 1.178949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:09:27Z"
    - latency: 1.221201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:08:27Z"
    - latency: 812.66µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:07:27Z"
    - latency: 1.322476ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:06:27Z"
    - latency: 1.738032ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:05:27Z"
    - latency: 773.617µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:04:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T05:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-9-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-9.ec2.internal
      uid: 0f639430-5a54-4ae9-8083-faf165506315
    resourceVersion: "22281"
    uid: b2491f74-ee40-434a-9172-a7ce62eddd33
  spec:
    sourcePod: network-check-source-869dcfcdcd-d82p2
    targetEndpoint: a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T05:09:27Z"
      message: 'load-balancer-api-external: tcp connection to a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.980986ms
      message: 'load-balancer-api-external: tcp connection to a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:09:27Z"
    - latency: 8.559354ms
      message: 'load-balancer-api-external: resolved host name a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T05:09:27Z"
    - latency: 4.113712ms
      message: 'load-balancer-api-external: tcp connection to a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:08:27Z"
    - latency: 8.58706ms
      message: 'load-balancer-api-external: resolved host name a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T05:08:27Z"
    - latency: 5.89664ms
      message: 'load-balancer-api-external: tcp connection to a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:07:27Z"
    - latency: 9.66948ms
      message: 'load-balancer-api-external: resolved host name a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T05:07:27Z"
    - latency: 5.759573ms
      message: 'load-balancer-api-external: tcp connection to a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:06:27Z"
    - latency: 9.043847ms
      message: 'load-balancer-api-external: resolved host name a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T05:06:27Z"
    - latency: 3.718796ms
      message: 'load-balancer-api-external: tcp connection to a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:05:27Z"
    - latency: 10.260385ms
      message: 'load-balancer-api-external: resolved host name a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T05:05:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T05:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-9-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-9.ec2.internal
      uid: 0f639430-5a54-4ae9-8083-faf165506315
    resourceVersion: "22280"
    uid: 65ccfbcd-a7e8-4245-921a-b6c9db379bf9
  spec:
    sourcePod: network-check-source-869dcfcdcd-d82p2
    targetEndpoint: a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T05:09:27Z"
      message: 'load-balancer-api-internal: tcp connection to a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.235619ms
      message: 'load-balancer-api-internal: tcp connection to a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:09:27Z"
    - latency: 8.526871ms
      message: 'load-balancer-api-internal: resolved host name a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T05:09:27Z"
    - latency: 4.064241ms
      message: 'load-balancer-api-internal: tcp connection to a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:08:27Z"
    - latency: 8.495966ms
      message: 'load-balancer-api-internal: resolved host name a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T05:08:27Z"
    - latency: 5.909256ms
      message: 'load-balancer-api-internal: tcp connection to a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:07:27Z"
    - latency: 9.617916ms
      message: 'load-balancer-api-internal: resolved host name a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T05:07:27Z"
    - latency: 5.78836ms
      message: 'load-balancer-api-internal: tcp connection to a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:06:27Z"
    - latency: 9.02801ms
      message: 'load-balancer-api-internal: resolved host name a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T05:06:27Z"
    - latency: 3.743219ms
      message: 'load-balancer-api-internal: tcp connection to a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:05:27Z"
    - latency: 10.015018ms
      message: 'load-balancer-api-internal: resolved host name a99a41e6ae03d42498b36316aa46dc0c-a066ff586d8ee6bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T05:05:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T05:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-9-to-network-check-target-ip-10-0-136-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-9.ec2.internal
      uid: 0f639430-5a54-4ae9-8083-faf165506315
    resourceVersion: "23508"
    uid: c3533792-10b4-4d41-afeb-7e969a0f4491
  spec:
    sourcePod: network-check-source-869dcfcdcd-d82p2
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T05:10:27Z"
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.042271ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:10:27Z"
    - latency: 1.112516ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:09:27Z"
    - latency: 1.186471ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:08:27Z"
    - latency: 1.52401ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:07:27Z"
    - latency: 766.613µs
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:06:27Z"
    - latency: 1.551349ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:05:27Z"
    - latency: 1.513512ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:04:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T05:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-9-to-network-check-target-ip-10-0-140-24
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-9.ec2.internal
      uid: 0f639430-5a54-4ae9-8083-faf165506315
    resourceVersion: "23509"
    uid: aa5a988a-6afe-45da-a81b-eb128c54d098
  spec:
    sourcePod: network-check-source-869dcfcdcd-d82p2
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T05:10:27Z"
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.289708ms
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:10:27Z"
    - latency: 2.324393ms
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:09:27Z"
    - latency: 2.656074ms
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:08:27Z"
    - latency: 2.29637ms
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:07:27Z"
    - latency: 2.017983ms
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:06:27Z"
    - latency: 2.403197ms
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:05:27Z"
    - latency: 1.949684ms
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:04:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T05:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-9-to-network-check-target-ip-10-0-142-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-9.ec2.internal
      uid: 0f639430-5a54-4ae9-8083-faf165506315
    resourceVersion: "23510"
    uid: 110fe7ac-6bb1-4a66-b0e6-b58fa9f5b123
  spec:
    sourcePod: network-check-source-869dcfcdcd-d82p2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T05:10:27Z"
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.263685ms
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:10:27Z"
    - latency: 2.348512ms
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:09:27Z"
    - latency: 2.625762ms
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:08:27Z"
    - latency: 2.64206ms
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:07:27Z"
    - latency: 2.302742ms
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:06:27Z"
    - latency: 2.312383ms
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:05:27Z"
    - latency: 2.215045ms
      message: 'network-check-target-ip-10-0-142-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:04:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T05:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-9-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-9.ec2.internal
      uid: 0f639430-5a54-4ae9-8083-faf165506315
    resourceVersion: "22279"
    uid: 84afc822-c2c4-4897-8446-2b4f307f56ff
  spec:
    sourcePod: network-check-source-869dcfcdcd-d82p2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T05:09:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 854.91µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:09:27Z"
    - latency: 1.826697ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T05:09:27Z"
    - latency: 1.045275ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:08:27Z"
    - latency: 1.678955ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T05:08:27Z"
    - latency: 970.296µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:07:27Z"
    - latency: 1.63109ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T05:07:27Z"
    - latency: 885.098µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:06:27Z"
    - latency: 1.685412ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T05:06:27Z"
    - latency: 855.465µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T05:05:27Z"
    - latency: 1.582159ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T05:05:27Z"
kind: List
metadata:
  resourceVersion: ""