apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:56:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-98-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-98.ec2.internal
      uid: 27c732b7-b33c-4fec-a101-6737e61821c5
    resourceVersion: "23397"
    uid: 3359e931-9b18-4839-9c8b-586570a573d9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-dflk5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:03:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.503627ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:03:46Z"
    - latency: 1.902107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:02:46Z"
    - latency: 1.116063ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:01:46Z"
    - latency: 1.204125ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:00:46Z"
    - latency: 1.056355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:59:46Z"
    - latency: 1.21415ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:58:46Z"
    - latency: 1.401704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:57:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:56:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-98-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-98.ec2.internal
      uid: 27c732b7-b33c-4fec-a101-6737e61821c5
    resourceVersion: "22197"
    uid: fdc82766-1353-40d7-94c2-7ca38e45c0f7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-dflk5
    targetEndpoint: a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:02:46Z"
      message: 'load-balancer-api-external: tcp connection to a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.763354ms
      message: 'load-balancer-api-external: tcp connection to a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:02:46Z"
    - latency: 7.325998ms
      message: 'load-balancer-api-external: resolved host name a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:02:46Z"
    - latency: 4.547366ms
      message: 'load-balancer-api-external: tcp connection to a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:01:46Z"
    - latency: 9.023803ms
      message: 'load-balancer-api-external: resolved host name a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:01:46Z"
    - latency: 4.886072ms
      message: 'load-balancer-api-external: tcp connection to a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:00:46Z"
    - latency: 7.28033ms
      message: 'load-balancer-api-external: resolved host name a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:00:46Z"
    - latency: 3.511628ms
      message: 'load-balancer-api-external: tcp connection to a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:59:46Z"
    - latency: 6.709789ms
      message: 'load-balancer-api-external: resolved host name a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:59:46Z"
    - latency: 4.978196ms
      message: 'load-balancer-api-external: tcp connection to a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:58:46Z"
    - latency: 6.52336ms
      message: 'load-balancer-api-external: resolved host name a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:58:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:56:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-98-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-98.ec2.internal
      uid: 27c732b7-b33c-4fec-a101-6737e61821c5
    resourceVersion: "22198"
    uid: b2eda9bf-7514-44b9-b2f3-5c5ebd46cccb
  spec:
    sourcePod: network-check-source-7bc5b6bf85-dflk5
    targetEndpoint: a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:02:46Z"
      message: 'load-balancer-api-internal: tcp connection to a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.717812ms
      message: 'load-balancer-api-internal: tcp connection to a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:02:46Z"
    - latency: 7.377575ms
      message: 'load-balancer-api-internal: resolved host name a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:02:46Z"
    - latency: 4.500545ms
      message: 'load-balancer-api-internal: tcp connection to a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:01:46Z"
    - latency: 9.116899ms
      message: 'load-balancer-api-internal: resolved host name a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:01:46Z"
    - latency: 4.91556ms
      message: 'load-balancer-api-internal: tcp connection to a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:00:46Z"
    - latency: 7.24784ms
      message: 'load-balancer-api-internal: resolved host name a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:00:46Z"
    - latency: 4.382276ms
      message: 'load-balancer-api-internal: tcp connection to a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:59:46Z"
    - latency: 6.674087ms
      message: 'load-balancer-api-internal: resolved host name a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:59:46Z"
    - latency: 4.907312ms
      message: 'load-balancer-api-internal: tcp connection to a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:58:46Z"
    - latency: 6.622855ms
      message: 'load-balancer-api-internal: resolved host name a93e2550bc877479091cf6e863a8e1a4-6f7819d24fdf918f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:58:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:56:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-98-to-network-check-target-ip-10-0-130-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-98.ec2.internal
      uid: 27c732b7-b33c-4fec-a101-6737e61821c5
    resourceVersion: "23396"
    uid: 73808f2d-98e5-4dc3-afaa-201ad07623aa
  spec:
    sourcePod: network-check-source-7bc5b6bf85-dflk5
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:03:46Z"
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.170965ms
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:03:46Z"
    - latency: 2.399243ms
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:02:46Z"
    - latency: 2.116185ms
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:01:46Z"
    - latency: 2.201855ms
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:00:46Z"
    - latency: 2.301279ms
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:59:46Z"
    - latency: 1.996633ms
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:58:46Z"
    - latency: 2.648908ms
      message: 'network-check-target-ip-10-0-130-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:57:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:56:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-98-to-network-check-target-ip-10-0-130-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-98.ec2.internal
      uid: 27c732b7-b33c-4fec-a101-6737e61821c5
    resourceVersion: "23394"
    uid: d8e05fd3-6165-4fa6-8781-d1e9d562d1fc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-dflk5
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:03:46Z"
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.097854ms
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:03:46Z"
    - latency: 899.301µs
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:02:46Z"
    - latency: 1.294801ms
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:01:46Z"
    - latency: 1.008987ms
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:00:46Z"
    - latency: 1.563434ms
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:59:46Z"
    - latency: 1.359749ms
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:58:46Z"
    - latency: 1.225465ms
      message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:57:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:56:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-98-to-network-check-target-ip-10-0-136-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-98.ec2.internal
      uid: 27c732b7-b33c-4fec-a101-6737e61821c5
    resourceVersion: "23395"
    uid: e1bda9e2-fd58-4c58-8a35-6a607018b361
  spec:
    sourcePod: network-check-source-7bc5b6bf85-dflk5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:03:46Z"
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.39656ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:03:46Z"
    - latency: 2.005245ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:02:46Z"
    - latency: 2.277117ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:01:46Z"
    - latency: 1.748971ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:00:46Z"
    - latency: 2.116188ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:59:46Z"
    - latency: 1.832874ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:58:46Z"
    - latency: 2.249801ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:57:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:56:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-98-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-98.ec2.internal
      uid: 27c732b7-b33c-4fec-a101-6737e61821c5
    resourceVersion: "22195"
    uid: a31e0092-6886-47ac-902b-beffd5e407d5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-dflk5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:02:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.036518ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:02:46Z"
    - latency: 2.342856ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:02:46Z"
    - latency: 919.993µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:01:46Z"
    - latency: 2.926435ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:01:46Z"
    - latency: 810.133µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:00:46Z"
    - latency: 1.66009ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:00:46Z"
    - latency: 1.312025ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:59:46Z"
    - latency: 1.676776ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:59:46Z"
    - latency: 980.878µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:58:46Z"
    - latency: 1.690211ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:58:46Z"
kind: List
metadata:
  resourceVersion: ""