apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T21:40:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-238-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-238.ec2.internal
      uid: 9215b15d-ae1d-4a8b-aa9a-1375efc8c6b6
    resourceVersion: "25240"
    uid: 523081fb-bf25-4ded-a0f8-fdd4352f5cfe
  spec:
    sourcePod: network-check-source-6947749cfc-fdjjv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T21:47:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.127887ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:47:02Z"
    - latency: 956.879µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:46:02Z"
    - latency: 1.213891ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:45:02Z"
    - latency: 1.162871ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:44:02Z"
    - latency: 2.708536ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:43:02Z"
    - latency: 1.711224ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:42:02Z"
    - latency: 1.035488ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:41:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T21:40:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-238-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-238.ec2.internal
      uid: 9215b15d-ae1d-4a8b-aa9a-1375efc8c6b6
    resourceVersion: "29237"
    uid: 302445e1-fd13-4f89-b640-b7e6b1e7c09b
  spec:
    sourcePod: network-check-source-6947749cfc-fdjjv
    targetEndpoint: aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T21:46:02Z"
      message: 'load-balancer-api-external: tcp connection to aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.500164ms
      message: 'load-balancer-api-external: tcp connection to aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:52:02Z"
    - latency: 6.791832ms
      message: 'load-balancer-api-external: resolved host name aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T21:52:02Z"
    - latency: 5.338893ms
      message: 'load-balancer-api-external: tcp connection to aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:51:02Z"
    - latency: 6.572486ms
      message: 'load-balancer-api-external: resolved host name aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T21:51:02Z"
    - latency: 5.165023ms
      message: 'load-balancer-api-external: tcp connection to aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:50:02Z"
    - latency: 9.738554ms
      message: 'load-balancer-api-external: resolved host name aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T21:50:02Z"
    - latency: 4.20743ms
      message: 'load-balancer-api-external: tcp connection to aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:49:02Z"
    - latency: 6.807921ms
      message: 'load-balancer-api-external: resolved host name aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T21:49:02Z"
    - latency: 5.522923ms
      message: 'load-balancer-api-external: tcp connection to aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:48:02Z"
    - latency: 6.824987ms
      message: 'load-balancer-api-external: resolved host name aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T21:48:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T21:40:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-238-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-238.ec2.internal
      uid: 9215b15d-ae1d-4a8b-aa9a-1375efc8c6b6
    resourceVersion: "29238"
    uid: d613fab0-93b9-468e-bc07-1f3d86963e6f
  spec:
    sourcePod: network-check-source-6947749cfc-fdjjv
    targetEndpoint: aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T21:46:02Z"
      message: 'load-balancer-api-internal: tcp connection to aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.595935ms
      message: 'load-balancer-api-internal: tcp connection to aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:52:02Z"
    - latency: 6.735884ms
      message: 'load-balancer-api-internal: resolved host name aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T21:52:02Z"
    - latency: 5.410757ms
      message: 'load-balancer-api-internal: tcp connection to aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:51:02Z"
    - latency: 6.379577ms
      message: 'load-balancer-api-internal: resolved host name aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T21:51:02Z"
    - latency: 5.155514ms
      message: 'load-balancer-api-internal: tcp connection to aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:50:02Z"
    - latency: 9.680738ms
      message: 'load-balancer-api-internal: resolved host name aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T21:50:02Z"
    - latency: 5.370817ms
      message: 'load-balancer-api-internal: tcp connection to aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:49:02Z"
    - latency: 6.861682ms
      message: 'load-balancer-api-internal: resolved host name aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T21:49:02Z"
    - latency: 5.500434ms
      message: 'load-balancer-api-internal: tcp connection to aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:48:02Z"
    - latency: 6.693783ms
      message: 'load-balancer-api-internal: resolved host name aad55f6b92b934c108b3737af48b2c34-3207be2188bc366b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T21:48:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T21:40:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-238-to-network-check-target-ip-10-0-128-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-238.ec2.internal
      uid: 9215b15d-ae1d-4a8b-aa9a-1375efc8c6b6
    resourceVersion: "25237"
    uid: 2e0e4b96-8725-40cc-93b9-e4dfdfcd2a9e
  spec:
    sourcePod: network-check-source-6947749cfc-fdjjv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T21:47:02Z"
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.324642ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:47:02Z"
    - latency: 2.030739ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:46:02Z"
    - latency: 1.997999ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:45:02Z"
    - latency: 2.021612ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:44:02Z"
    - latency: 3.051119ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:43:02Z"
    - latency: 1.959775ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:42:02Z"
    - latency: 1.822007ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:41:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T21:40:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-238-to-network-check-target-ip-10-0-135-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-238.ec2.internal
      uid: 9215b15d-ae1d-4a8b-aa9a-1375efc8c6b6
    resourceVersion: "25238"
    uid: e13c4a32-70b8-4e60-b60a-06984b7955eb
  spec:
    sourcePod: network-check-source-6947749cfc-fdjjv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T21:47:02Z"
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.135598ms
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:47:02Z"
    - latency: 797.396µs
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:46:02Z"
    - latency: 811.09µs
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:45:02Z"
    - latency: 877.483µs
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:44:02Z"
    - latency: 1.208409ms
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:43:02Z"
    - latency: 1.078922ms
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:42:02Z"
    - latency: 1.18739ms
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:41:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T21:40:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-238-to-network-check-target-ip-10-0-142-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-238.ec2.internal
      uid: 9215b15d-ae1d-4a8b-aa9a-1375efc8c6b6
    resourceVersion: "25239"
    uid: 59092f1e-6d26-456e-b727-3dbbeef74cc9
  spec:
    sourcePod: network-check-source-6947749cfc-fdjjv
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T21:47:02Z"
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.135187ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:47:02Z"
    - latency: 2.235663ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:46:02Z"
    - latency: 2.098488ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:45:02Z"
    - latency: 1.934996ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:44:02Z"
    - latency: 2.269305ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:43:02Z"
    - latency: 2.585431ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:42:02Z"
    - latency: 2.155956ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:41:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T21:40:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-238-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-238.ec2.internal
      uid: 9215b15d-ae1d-4a8b-aa9a-1375efc8c6b6
    resourceVersion: "29236"
    uid: 7d591a03-0346-46a6-bf69-5f69c55bd577
  spec:
    sourcePod: network-check-source-6947749cfc-fdjjv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T21:46:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 858.753µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:52:02Z"
    - latency: 1.731743ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T21:52:02Z"
    - latency: 998.429µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:51:02Z"
    - latency: 1.610675ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T21:51:02Z"
    - latency: 1.03479ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:50:02Z"
    - latency: 1.951664ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T21:50:02Z"
    - latency: 894.742µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:49:02Z"
    - latency: 1.76208ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T21:49:02Z"
    - latency: 800.119µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T21:48:02Z"
    - latency: 1.764084ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T21:48:02Z"
kind: List
metadata:
  resourceVersion: ""