apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T06:31:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-5-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-5.ec2.internal
      uid: 1d14f477-5353-47d3-8e79-32ebb1e2fcd6
    resourceVersion: "14615"
    uid: c11e4122-03fd-4fb5-b0c4-8f8ca975a49b
  spec:
    sourcePod: network-check-source-7d88cb55d8-cd58q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T06:38:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 918.718µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:38:28Z"
    - latency: 1.135861ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:37:28Z"
    - latency: 913.891µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:36:28Z"
    - latency: 1.034056ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:35:28Z"
    - latency: 780.882µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:34:28Z"
    - latency: 912.978µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:33:28Z"
    - latency: 1.540712ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:32:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T06:31:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-5-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-5.ec2.internal
      uid: 1d14f477-5353-47d3-8e79-32ebb1e2fcd6
    resourceVersion: "14283"
    uid: 87a7dec9-240c-4ee6-9132-23b82ddcac7a
  spec:
    sourcePod: network-check-source-7d88cb55d8-cd58q
    targetEndpoint: a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T06:37:28Z"
      message: 'load-balancer-api-external: tcp connection to a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.088719ms
      message: 'load-balancer-api-external: tcp connection to a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:37:28Z"
    - latency: 11.757863ms
      message: 'load-balancer-api-external: resolved host name a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T06:37:28Z"
    - latency: 5.235989ms
      message: 'load-balancer-api-external: tcp connection to a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:36:28Z"
    - latency: 8.917118ms
      message: 'load-balancer-api-external: resolved host name a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T06:36:28Z"
    - latency: 5.36627ms
      message: 'load-balancer-api-external: tcp connection to a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:35:28Z"
    - latency: 8.236881ms
      message: 'load-balancer-api-external: resolved host name a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T06:35:28Z"
    - latency: 4.626734ms
      message: 'load-balancer-api-external: tcp connection to a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:34:28Z"
    - latency: 7.784223ms
      message: 'load-balancer-api-external: resolved host name a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T06:34:28Z"
    - latency: 5.059547ms
      message: 'load-balancer-api-external: tcp connection to a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:33:28Z"
    - latency: 9.735184ms
      message: 'load-balancer-api-external: resolved host name a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T06:33:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T06:31:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-5-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-5.ec2.internal
      uid: 1d14f477-5353-47d3-8e79-32ebb1e2fcd6
    resourceVersion: "14282"
    uid: a83e6b07-89ee-45cb-8f2f-6c220bc3f4ca
  spec:
    sourcePod: network-check-source-7d88cb55d8-cd58q
    targetEndpoint: a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T06:37:28Z"
      message: 'load-balancer-api-internal: tcp connection to a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.122327ms
      message: 'load-balancer-api-internal: tcp connection to a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:37:28Z"
    - latency: 11.68916ms
      message: 'load-balancer-api-internal: resolved host name a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T06:37:28Z"
    - latency: 5.268912ms
      message: 'load-balancer-api-internal: tcp connection to a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:36:28Z"
    - latency: 8.88841ms
      message: 'load-balancer-api-internal: resolved host name a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T06:36:28Z"
    - latency: 5.335747ms
      message: 'load-balancer-api-internal: tcp connection to a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:35:28Z"
    - latency: 8.17808ms
      message: 'load-balancer-api-internal: resolved host name a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T06:35:28Z"
    - latency: 4.297877ms
      message: 'load-balancer-api-internal: tcp connection to a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:34:28Z"
    - latency: 7.830615ms
      message: 'load-balancer-api-internal: resolved host name a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T06:34:28Z"
    - latency: 4.84777ms
      message: 'load-balancer-api-internal: tcp connection to a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:33:28Z"
    - latency: 9.623993ms
      message: 'load-balancer-api-internal: resolved host name a5f2d86fbd34f4e5fb8774b88f8fabed-48a13af4dd3a737a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T06:33:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T06:31:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-5-to-network-check-target-ip-10-0-136-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-5.ec2.internal
      uid: 1d14f477-5353-47d3-8e79-32ebb1e2fcd6
    resourceVersion: "14613"
    uid: 534d9ac3-8016-44b6-82db-97413d18c4c6
  spec:
    sourcePod: network-check-source-7d88cb55d8-cd58q
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T06:38:28Z"
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.904082ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:38:28Z"
    - latency: 1.932948ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:37:28Z"
    - latency: 1.851719ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:36:28Z"
    - latency: 1.909626ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:35:28Z"
    - latency: 1.80989ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:34:28Z"
    - latency: 1.660173ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:33:28Z"
    - latency: 1.966628ms
      message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:32:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T06:31:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-5-to-network-check-target-ip-10-0-136-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-5.ec2.internal
      uid: 1d14f477-5353-47d3-8e79-32ebb1e2fcd6
    resourceVersion: "14614"
    uid: a71e2a82-9cd1-4703-91c9-442a7ac4c595
  spec:
    sourcePod: network-check-source-7d88cb55d8-cd58q
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T06:38:28Z"
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.315317ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:38:28Z"
    - latency: 2.269617ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:37:28Z"
    - latency: 2.310068ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:36:28Z"
    - latency: 2.089565ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:35:28Z"
    - latency: 1.970026ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:34:28Z"
    - latency: 2.162548ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:33:28Z"
    - latency: 2.430835ms
      message: 'network-check-target-ip-10-0-136-235: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:32:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T06:31:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-5-to-network-check-target-ip-10-0-142-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-5.ec2.internal
      uid: 1d14f477-5353-47d3-8e79-32ebb1e2fcd6
    resourceVersion: "14612"
    uid: 6d5ea609-077b-408c-9c4e-a4378a39d946
  spec:
    sourcePod: network-check-source-7d88cb55d8-cd58q
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T06:38:28Z"
      message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 997.785µs
      message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:38:28Z"
    - latency: 930.188µs
      message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:37:28Z"
    - latency: 818.074µs
      message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:36:28Z"
    - latency: 965.631µs
      message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:35:28Z"
    - latency: 1.281538ms
      message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:34:28Z"
    - latency: 1.003027ms
      message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:33:28Z"
    - latency: 1.995097ms
      message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:32:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T06:31:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-5-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-5.ec2.internal
      uid: 1d14f477-5353-47d3-8e79-32ebb1e2fcd6
    resourceVersion: "14281"
    uid: e7d85082-f1fd-42fa-b331-c833b8fe1881
  spec:
    sourcePod: network-check-source-7d88cb55d8-cd58q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T06:37:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 841.697µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:37:28Z"
    - latency: 1.727179ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T06:37:28Z"
    - latency: 1.255034ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:36:28Z"
    - latency: 1.644941ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T06:36:28Z"
    - latency: 916.602µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:35:28Z"
    - latency: 2.056303ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T06:35:28Z"
    - latency: 830.374µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:34:28Z"
    - latency: 1.738664ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T06:34:28Z"
    - latency: 979.634µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T06:33:28Z"
    - latency: 2.212528ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T06:33:28Z"
kind: List
metadata:
  resourceVersion: ""