apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-212-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-212.ec2.internal
      uid: 753d4d2f-54ec-4fda-99d8-300a9d754561
    resourceVersion: "22669"
    uid: 12c57177-849e-44c2-b9c9-daf5053a1e15
  spec:
    sourcePod: network-check-source-56499946bc-nl9rp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:27:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.210565ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:27:10Z"
    - latency: 1.149791ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:26:10Z"
    - latency: 875.606µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:25:10Z"
    - latency: 954.471µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:24:10Z"
    - latency: 1.362698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:23:10Z"
    - latency: 1.108304ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:22:10Z"
    - latency: 1.078045ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:21:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-212-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-212.ec2.internal
      uid: 753d4d2f-54ec-4fda-99d8-300a9d754561
    resourceVersion: "21507"
    uid: 6c9bdc02-4b52-4584-9445-ed9a240ebcac
  spec:
    sourcePod: network-check-source-56499946bc-nl9rp
    targetEndpoint: a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:26:10Z"
      message: 'load-balancer-api-external: tcp connection to a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.555786ms
      message: 'load-balancer-api-external: tcp connection to a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:26:10Z"
    - latency: 13.015925ms
      message: 'load-balancer-api-external: resolved host name a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:26:10Z"
    - latency: 4.210195ms
      message: 'load-balancer-api-external: tcp connection to a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:25:10Z"
    - latency: 7.937729ms
      message: 'load-balancer-api-external: resolved host name a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:25:10Z"
    - latency: 6.680021ms
      message: 'load-balancer-api-external: tcp connection to a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:24:10Z"
    - latency: 8.439484ms
      message: 'load-balancer-api-external: resolved host name a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:24:10Z"
    - latency: 5.490049ms
      message: 'load-balancer-api-external: tcp connection to a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:23:10Z"
    - latency: 8.28034ms
      message: 'load-balancer-api-external: resolved host name a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:23:10Z"
    - latency: 4.993556ms
      message: 'load-balancer-api-external: tcp connection to a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:22:10Z"
    - latency: 6.714183ms
      message: 'load-balancer-api-external: resolved host name a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:22:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-212-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-212.ec2.internal
      uid: 753d4d2f-54ec-4fda-99d8-300a9d754561
    resourceVersion: "21506"
    uid: 291f4f1a-e53b-485d-9561-8ae566872031
  spec:
    sourcePod: network-check-source-56499946bc-nl9rp
    targetEndpoint: a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:26:10Z"
      message: 'load-balancer-api-internal: tcp connection to a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.52924ms
      message: 'load-balancer-api-internal: tcp connection to a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:26:10Z"
    - latency: 13.099341ms
      message: 'load-balancer-api-internal: resolved host name a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:26:10Z"
    - latency: 4.181346ms
      message: 'load-balancer-api-internal: tcp connection to a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:25:10Z"
    - latency: 8.05677ms
      message: 'load-balancer-api-internal: resolved host name a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:25:10Z"
    - latency: 5.625118ms
      message: 'load-balancer-api-internal: tcp connection to a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:24:10Z"
    - latency: 8.410562ms
      message: 'load-balancer-api-internal: resolved host name a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:24:10Z"
    - latency: 5.413584ms
      message: 'load-balancer-api-internal: tcp connection to a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:23:10Z"
    - latency: 8.358974ms
      message: 'load-balancer-api-internal: resolved host name a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:23:10Z"
    - latency: 4.821645ms
      message: 'load-balancer-api-internal: tcp connection to a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:22:10Z"
    - latency: 6.753458ms
      message: 'load-balancer-api-internal: resolved host name a07adf43fa32e4e8380f4bcfc77338f5-289909de1e58b9bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:22:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-212-to-network-check-target-ip-10-0-131-212
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-212.ec2.internal
      uid: 753d4d2f-54ec-4fda-99d8-300a9d754561
    resourceVersion: "22666"
    uid: fe9b6d49-e6b6-4547-986f-c2cb5176e221
  spec:
    sourcePod: network-check-source-56499946bc-nl9rp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:27:10Z"
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 942.583µs
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:27:10Z"
    - latency: 1.019349ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:26:10Z"
    - latency: 897.159µs
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:25:10Z"
    - latency: 961.419µs
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:24:10Z"
    - latency: 827.956µs
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:23:10Z"
    - latency: 955.051µs
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:22:10Z"
    - latency: 1.419663ms
      message: 'network-check-target-ip-10-0-131-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:21:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-212-to-network-check-target-ip-10-0-140-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-212.ec2.internal
      uid: 753d4d2f-54ec-4fda-99d8-300a9d754561
    resourceVersion: "22668"
    uid: f2550481-7abf-4dec-996d-15da016c3557
  spec:
    sourcePod: network-check-source-56499946bc-nl9rp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:27:10Z"
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.142131ms
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:27:10Z"
    - latency: 2.219321ms
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:26:10Z"
    - latency: 1.751476ms
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:25:10Z"
    - latency: 1.908838ms
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:24:10Z"
    - latency: 2.465949ms
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:23:10Z"
    - latency: 2.288758ms
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:22:10Z"
    - latency: 2.192876ms
      message: 'network-check-target-ip-10-0-140-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:21:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-212-to-network-check-target-ip-10-0-141-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-212.ec2.internal
      uid: 753d4d2f-54ec-4fda-99d8-300a9d754561
    resourceVersion: "22667"
    uid: 799d0a22-10bc-4902-8a15-5192806066b8
  spec:
    sourcePod: network-check-source-56499946bc-nl9rp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:27:10Z"
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.871304ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:27:10Z"
    - latency: 2.147359ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:26:10Z"
    - latency: 1.814933ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:25:10Z"
    - latency: 1.717773ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:24:10Z"
    - latency: 1.707192ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:23:10Z"
    - latency: 1.858514ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:22:10Z"
    - latency: 2.218879ms
      message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:21:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T20:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-212-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-212.ec2.internal
      uid: 753d4d2f-54ec-4fda-99d8-300a9d754561
    resourceVersion: "21505"
    uid: d4bc778e-de1a-4596-9122-a2b72dc1373f
  spec:
    sourcePod: network-check-source-56499946bc-nl9rp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T20:26:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.704µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:26:10Z"
    - latency: 1.912894ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:26:10Z"
    - latency: 896.845µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:25:10Z"
    - latency: 1.779535ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:25:10Z"
    - latency: 1.034606ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:24:10Z"
    - latency: 1.655375ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:24:10Z"
    - latency: 1.167965ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:23:10Z"
    - latency: 2.054804ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:23:10Z"
    - latency: 913.444µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T20:22:10Z"
    - latency: 1.893335ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T20:22:10Z"
kind: List
metadata:
  resourceVersion: ""