apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T11:43:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-138-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-138.ec2.internal
      uid: ebe9768b-1e04-4a37-b7cb-0bb6920a623a
    resourceVersion: "14875"
    uid: 710c9bfb-e782-4feb-a938-22b420c1ce2b
  spec:
    sourcePod: network-check-source-7f44b6dd87-hcfd9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T11:50:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 991.349µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:50:06Z"
    - latency: 827.222µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:49:06Z"
    - latency: 1.124579ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:48:06Z"
    - latency: 1.134135ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:47:06Z"
    - latency: 1.320563ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:46:06Z"
    - latency: 2.060435ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:45:06Z"
    - latency: 901.869µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:44:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T11:43:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-138-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-138.ec2.internal
      uid: ebe9768b-1e04-4a37-b7cb-0bb6920a623a
    resourceVersion: "14443"
    uid: d33af1fe-26e3-47d9-8aee-27029c738544
  spec:
    sourcePod: network-check-source-7f44b6dd87-hcfd9
    targetEndpoint: a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T11:49:06Z"
      message: 'load-balancer-api-external: tcp connection to a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.760031ms
      message: 'load-balancer-api-external: tcp connection to a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:49:06Z"
    - latency: 7.794417ms
      message: 'load-balancer-api-external: resolved host name a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:49:06Z"
    - latency: 4.603874ms
      message: 'load-balancer-api-external: tcp connection to a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:48:06Z"
    - latency: 8.112789ms
      message: 'load-balancer-api-external: resolved host name a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:48:06Z"
    - latency: 4.670057ms
      message: 'load-balancer-api-external: tcp connection to a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:47:06Z"
    - latency: 8.261166ms
      message: 'load-balancer-api-external: resolved host name a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:47:06Z"
    - latency: 4.980154ms
      message: 'load-balancer-api-external: tcp connection to a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:46:06Z"
    - latency: 9.876703ms
      message: 'load-balancer-api-external: resolved host name a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:46:06Z"
    - latency: 4.444637ms
      message: 'load-balancer-api-external: tcp connection to a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:45:06Z"
    - latency: 10.187675ms
      message: 'load-balancer-api-external: resolved host name a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:45:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T11:43:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-138-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-138.ec2.internal
      uid: ebe9768b-1e04-4a37-b7cb-0bb6920a623a
    resourceVersion: "14444"
    uid: ddb7ebf5-1e16-45f9-98fd-575d5c2b51c7
  spec:
    sourcePod: network-check-source-7f44b6dd87-hcfd9
    targetEndpoint: a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T11:49:06Z"
      message: 'load-balancer-api-internal: tcp connection to a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.831608ms
      message: 'load-balancer-api-internal: tcp connection to a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:49:06Z"
    - latency: 7.722201ms
      message: 'load-balancer-api-internal: resolved host name a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:49:06Z"
    - latency: 5.619614ms
      message: 'load-balancer-api-internal: tcp connection to a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:48:06Z"
    - latency: 8.074128ms
      message: 'load-balancer-api-internal: resolved host name a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:48:06Z"
    - latency: 5.773394ms
      message: 'load-balancer-api-internal: tcp connection to a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:47:06Z"
    - latency: 8.2271ms
      message: 'load-balancer-api-internal: resolved host name a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:47:06Z"
    - latency: 3.917982ms
      message: 'load-balancer-api-internal: tcp connection to a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:46:06Z"
    - latency: 9.799832ms
      message: 'load-balancer-api-internal: resolved host name a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:46:06Z"
    - latency: 4.912773ms
      message: 'load-balancer-api-internal: tcp connection to a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:45:06Z"
    - latency: 9.914172ms
      message: 'load-balancer-api-internal: resolved host name a49e6a01e671f4fdc9d582f111c6554f-7d178a5924e4d67e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:45:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T11:43:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-138-to-network-check-target-ip-10-0-132-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-138.ec2.internal
      uid: ebe9768b-1e04-4a37-b7cb-0bb6920a623a
    resourceVersion: "14871"
    uid: 147802f1-b80a-490e-9d21-c1f4d08d1c62
  spec:
    sourcePod: network-check-source-7f44b6dd87-hcfd9
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T11:50:06Z"
      message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 889.721µs
      message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:50:06Z"
    - latency: 822.807µs
      message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:49:06Z"
    - latency: 1.267147ms
      message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:48:06Z"
    - latency: 1.247491ms
      message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:47:06Z"
    - latency: 879.758µs
      message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:46:06Z"
    - latency: 2.507949ms
      message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:45:06Z"
    - latency: 1.270971ms
      message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:44:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T11:43:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-138-to-network-check-target-ip-10-0-137-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-138.ec2.internal
      uid: ebe9768b-1e04-4a37-b7cb-0bb6920a623a
    resourceVersion: "14872"
    uid: 7a37eec7-c867-4b63-a7f4-617a97ca6aea
  spec:
    sourcePod: network-check-source-7f44b6dd87-hcfd9
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T11:50:06Z"
      message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.867972ms
      message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:50:06Z"
    - latency: 1.737392ms
      message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:49:06Z"
    - latency: 1.668095ms
      message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:48:06Z"
    - latency: 1.816325ms
      message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:47:06Z"
    - latency: 2.279896ms
      message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:46:06Z"
    - latency: 2.576549ms
      message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:45:06Z"
    - latency: 2.0289ms
      message: 'network-check-target-ip-10-0-137-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:44:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T11:43:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-138-to-network-check-target-ip-10-0-139-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-138.ec2.internal
      uid: ebe9768b-1e04-4a37-b7cb-0bb6920a623a
    resourceVersion: "14873"
    uid: bf25a35b-328e-40e0-ac06-cf78f1361fa7
  spec:
    sourcePod: network-check-source-7f44b6dd87-hcfd9
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T11:50:06Z"
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.982075ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:50:06Z"
    - latency: 2.144642ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:49:06Z"
    - latency: 1.872101ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:48:06Z"
    - latency: 2.120858ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:47:06Z"
    - latency: 1.856751ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:46:06Z"
    - latency: 2.426427ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:45:06Z"
    - latency: 2.385751ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:44:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T11:43:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-138-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-138.ec2.internal
      uid: ebe9768b-1e04-4a37-b7cb-0bb6920a623a
    resourceVersion: "14442"
    uid: eb163452-d9df-4f4b-82bd-cdc7790ef88a
  spec:
    sourcePod: network-check-source-7f44b6dd87-hcfd9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T11:49:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 823.781µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:49:06Z"
    - latency: 1.803886ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:49:06Z"
    - latency: 804.498µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:48:06Z"
    - latency: 1.855168ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:48:06Z"
    - latency: 1.160469ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:47:06Z"
    - latency: 1.729136ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:47:06Z"
    - latency: 740.355µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:46:06Z"
    - latency: 1.909223ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:46:06Z"
    - latency: 938.992µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T11:45:06Z"
    - latency: 3.108399ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T11:45:06Z"
kind: List
metadata:
  resourceVersion: ""