apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T17:04:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-235-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-235.ec2.internal
      uid: 49123464-ff4b-42b2-aec3-bd2e2f70cf3b
    resourceVersion: "14118"
    uid: fe12000a-16f7-495c-b788-794dcd5ef821
  spec:
    sourcePod: network-check-source-56d84b9f44-4b5fp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T17:11:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 964.369µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:11:40Z"
    - latency: 1.340044ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:10:40Z"
    - latency: 1.193775ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:09:40Z"
    - latency: 827.441µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:08:40Z"
    - latency: 790.738µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:07:40Z"
    - latency: 937.431µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:06:40Z"
    - latency: 970.781µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:05:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T17:04:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-235-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-235.ec2.internal
      uid: 49123464-ff4b-42b2-aec3-bd2e2f70cf3b
    resourceVersion: "13786"
    uid: 59f6323a-0b48-4084-a0e9-23ad4357fbe6
  spec:
    sourcePod: network-check-source-56d84b9f44-4b5fp
    targetEndpoint: a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T17:10:40Z"
      message: 'load-balancer-api-external: tcp connection to a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.545988ms
      message: 'load-balancer-api-external: tcp connection to a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:10:40Z"
    - latency: 9.666305ms
      message: 'load-balancer-api-external: resolved host name a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:10:40Z"
    - latency: 5.581589ms
      message: 'load-balancer-api-external: tcp connection to a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:09:40Z"
    - latency: 8.212504ms
      message: 'load-balancer-api-external: resolved host name a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:09:40Z"
    - latency: 5.959734ms
      message: 'load-balancer-api-external: tcp connection to a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:08:40Z"
    - latency: 10.187088ms
      message: 'load-balancer-api-external: resolved host name a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:08:40Z"
    - latency: 3.623699ms
      message: 'load-balancer-api-external: tcp connection to a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:07:40Z"
    - latency: 9.077899ms
      message: 'load-balancer-api-external: resolved host name a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:07:40Z"
    - latency: 4.33843ms
      message: 'load-balancer-api-external: tcp connection to a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:06:40Z"
    - latency: 9.505664ms
      message: 'load-balancer-api-external: resolved host name a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:06:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T17:04:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-235-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-235.ec2.internal
      uid: 49123464-ff4b-42b2-aec3-bd2e2f70cf3b
    resourceVersion: "13787"
    uid: 13f3beb9-b94a-4838-b024-aeff1a4c0b60
  spec:
    sourcePod: network-check-source-56d84b9f44-4b5fp
    targetEndpoint: a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T17:10:40Z"
      message: 'load-balancer-api-internal: tcp connection to a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.503466ms
      message: 'load-balancer-api-internal: tcp connection to a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:10:40Z"
    - latency: 9.660166ms
      message: 'load-balancer-api-internal: resolved host name a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:10:40Z"
    - latency: 4.968658ms
      message: 'load-balancer-api-internal: tcp connection to a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:09:40Z"
    - latency: 8.232638ms
      message: 'load-balancer-api-internal: resolved host name a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:09:40Z"
    - latency: 5.91756ms
      message: 'load-balancer-api-internal: tcp connection to a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:08:40Z"
    - latency: 10.224162ms
      message: 'load-balancer-api-internal: resolved host name a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:08:40Z"
    - latency: 4.263492ms
      message: 'load-balancer-api-internal: tcp connection to a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:07:40Z"
    - latency: 9.132933ms
      message: 'load-balancer-api-internal: resolved host name a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:07:40Z"
    - latency: 5.191745ms
      message: 'load-balancer-api-internal: tcp connection to a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:06:40Z"
    - latency: 9.550621ms
      message: 'load-balancer-api-internal: resolved host name a78f9db0e0c304b5fa9c8de2bf8e0fcd-f13cb2e201c46015.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:06:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T17:04:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-235-to-network-check-target-ip-10-0-135-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-235.ec2.internal
      uid: 49123464-ff4b-42b2-aec3-bd2e2f70cf3b
    resourceVersion: "14116"
    uid: bde63cea-2ec3-40a6-b37b-ec0635f66bde
  spec:
    sourcePod: network-check-source-56d84b9f44-4b5fp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T17:11:40Z"
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 886.585µs
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:11:40Z"
    - latency: 764.414µs
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:10:40Z"
    - latency: 846.637µs
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:09:40Z"
    - latency: 794.463µs
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:08:40Z"
    - latency: 928.848µs
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:07:40Z"
    - latency: 1.218238ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:06:40Z"
    - latency: 1.684735ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:05:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T17:04:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-235-to-network-check-target-ip-10-0-136-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-235.ec2.internal
      uid: 49123464-ff4b-42b2-aec3-bd2e2f70cf3b
    resourceVersion: "14115"
    uid: 289bf1b5-ef0b-4190-8c85-b2f81a83469a
  spec:
    sourcePod: network-check-source-56d84b9f44-4b5fp
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T17:11:40Z"
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.208958ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:11:40Z"
    - latency: 2.167246ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:10:40Z"
    - latency: 1.916925ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:09:40Z"
    - latency: 1.891826ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:08:40Z"
    - latency: 1.91663ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:07:40Z"
    - latency: 2.140305ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:06:40Z"
    - latency: 2.235619ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:05:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T17:04:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-235-to-network-check-target-ip-10-0-141-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-235.ec2.internal
      uid: 49123464-ff4b-42b2-aec3-bd2e2f70cf3b
    resourceVersion: "14117"
    uid: d529ee8a-50a6-4a30-87b7-e534043520d5
  spec:
    sourcePod: network-check-source-56d84b9f44-4b5fp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T17:11:40Z"
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.004954ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:11:40Z"
    - latency: 1.830388ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:10:40Z"
    - latency: 1.984399ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:09:40Z"
    - latency: 1.763176ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:08:40Z"
    - latency: 1.588372ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:07:40Z"
    - latency: 1.89018ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:06:40Z"
    - latency: 2.042252ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:05:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T17:04:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-235-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-235.ec2.internal
      uid: 49123464-ff4b-42b2-aec3-bd2e2f70cf3b
    resourceVersion: "13785"
    uid: 8a675586-1e3f-42eb-a917-f017d5372701
  spec:
    sourcePod: network-check-source-56d84b9f44-4b5fp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T17:10:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 846.343µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:10:40Z"
    - latency: 2.395577ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:10:40Z"
    - latency: 1.012475ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:09:40Z"
    - latency: 1.627266ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:09:40Z"
    - latency: 768.227µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:08:40Z"
    - latency: 1.756518ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:08:40Z"
    - latency: 747.252µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:07:40Z"
    - latency: 1.880886ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:07:40Z"
    - latency: 924.692µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:06:40Z"
    - latency: 1.814135ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:06:40Z"
kind: List
metadata:
  resourceVersion: ""