apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:41:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-144-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-144.ec2.internal
      uid: 2b399071-d1ed-4251-8c13-9d810fc6060f
    resourceVersion: "14508"
    uid: 45bfe645-5bb5-4560-bfd1-b0b929b123aa
  spec:
    sourcePod: network-check-source-65bdbbff45-k7sp7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:48:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 967.936µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:48:24Z"
    - latency: 1.348314ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:47:24Z"
    - latency: 1.282494ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:46:24Z"
    - latency: 901.217µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:45:24Z"
    - latency: 1.47686ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:44:24Z"
    - latency: 1.046384ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:43:24Z"
    - latency: 1.043421ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:42:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:41:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-144-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-144.ec2.internal
      uid: 2b399071-d1ed-4251-8c13-9d810fc6060f
    resourceVersion: "14068"
    uid: f5ecb01d-cf43-46a8-a676-9e43375b856c
  spec:
    sourcePod: network-check-source-65bdbbff45-k7sp7
    targetEndpoint: a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:47:24Z"
      message: 'load-balancer-api-external: tcp connection to a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.197928ms
      message: 'load-balancer-api-external: tcp connection to a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:47:24Z"
    - latency: 7.094508ms
      message: 'load-balancer-api-external: resolved host name a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:47:24Z"
    - latency: 3.431831ms
      message: 'load-balancer-api-external: tcp connection to a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:46:24Z"
    - latency: 7.27665ms
      message: 'load-balancer-api-external: resolved host name a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:46:24Z"
    - latency: 4.431781ms
      message: 'load-balancer-api-external: tcp connection to a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:45:24Z"
    - latency: 8.275845ms
      message: 'load-balancer-api-external: resolved host name a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:45:24Z"
    - latency: 5.414603ms
      message: 'load-balancer-api-external: tcp connection to a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:44:24Z"
    - latency: 8.415316ms
      message: 'load-balancer-api-external: resolved host name a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:44:24Z"
    - latency: 5.957167ms
      message: 'load-balancer-api-external: tcp connection to a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:43:24Z"
    - latency: 8.578444ms
      message: 'load-balancer-api-external: resolved host name a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:43:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:41:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-144-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-144.ec2.internal
      uid: 2b399071-d1ed-4251-8c13-9d810fc6060f
    resourceVersion: "14067"
    uid: 103ed1b2-21e5-408d-8dc6-edf196b0aa7d
  spec:
    sourcePod: network-check-source-65bdbbff45-k7sp7
    targetEndpoint: a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:47:24Z"
      message: 'load-balancer-api-internal: tcp connection to a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.216607ms
      message: 'load-balancer-api-internal: tcp connection to a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:47:24Z"
    - latency: 7.034339ms
      message: 'load-balancer-api-internal: resolved host name a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:47:24Z"
    - latency: 4.459083ms
      message: 'load-balancer-api-internal: tcp connection to a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:46:24Z"
    - latency: 7.428632ms
      message: 'load-balancer-api-internal: resolved host name a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:46:24Z"
    - latency: 3.734518ms
      message: 'load-balancer-api-internal: tcp connection to a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:45:24Z"
    - latency: 8.316675ms
      message: 'load-balancer-api-internal: resolved host name a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:45:24Z"
    - latency: 5.440381ms
      message: 'load-balancer-api-internal: tcp connection to a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:44:24Z"
    - latency: 8.354952ms
      message: 'load-balancer-api-internal: resolved host name a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:44:24Z"
    - latency: 4.859096ms
      message: 'load-balancer-api-internal: tcp connection to a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:43:24Z"
    - latency: 8.556699ms
      message: 'load-balancer-api-internal: resolved host name a2a7bef4924034215ae2a865b2e09ba4-3b69281aa81c3f48.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:43:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:41:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-144-to-network-check-target-ip-10-0-133-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-144.ec2.internal
      uid: 2b399071-d1ed-4251-8c13-9d810fc6060f
    resourceVersion: "14507"
    uid: ebff676f-3d13-4205-a120-fccbca78391c
  spec:
    sourcePod: network-check-source-65bdbbff45-k7sp7
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:48:24Z"
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.027527ms
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:48:24Z"
    - latency: 2.505376ms
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:47:24Z"
    - latency: 2.134022ms
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:46:24Z"
    - latency: 2.176383ms
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:45:24Z"
    - latency: 2.381299ms
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:44:24Z"
    - latency: 2.228326ms
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:43:24Z"
    - latency: 2.426061ms
      message: 'network-check-target-ip-10-0-133-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:42:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:41:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-144-to-network-check-target-ip-10-0-141-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-144.ec2.internal
      uid: 2b399071-d1ed-4251-8c13-9d810fc6060f
    resourceVersion: "14505"
    uid: a2e1dbee-c8f8-407a-beb0-f1ba222f9632
  spec:
    sourcePod: network-check-source-65bdbbff45-k7sp7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:48:24Z"
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.08867ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:48:24Z"
    - latency: 1.671254ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:47:24Z"
    - latency: 1.778796ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:46:24Z"
    - latency: 2.416778ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:45:24Z"
    - latency: 1.913296ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:44:24Z"
    - latency: 1.938438ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:43:24Z"
    - latency: 1.680652ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:42:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:41:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-144-to-network-check-target-ip-10-0-142-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-144.ec2.internal
      uid: 2b399071-d1ed-4251-8c13-9d810fc6060f
    resourceVersion: "14506"
    uid: 681a3a51-f62a-470a-8b1f-3d7d8dd3839a
  spec:
    sourcePod: network-check-source-65bdbbff45-k7sp7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:48:24Z"
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.640496ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:48:24Z"
    - latency: 1.628605ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:47:24Z"
    - latency: 1.00029ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:46:24Z"
    - latency: 1.738229ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:45:24Z"
    - latency: 758.699µs
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:44:24Z"
    - latency: 1.352967ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:43:24Z"
    - latency: 1.697304ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:42:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:41:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-144-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-144.ec2.internal
      uid: 2b399071-d1ed-4251-8c13-9d810fc6060f
    resourceVersion: "14066"
    uid: d76e4d95-21f5-4387-a02c-95cf56e7965e
  spec:
    sourcePod: network-check-source-65bdbbff45-k7sp7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:47:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.028519ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:47:24Z"
    - latency: 2.11253ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:47:24Z"
    - latency: 1.427059ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:46:24Z"
    - latency: 1.834503ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:46:24Z"
    - latency: 782.184µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:45:24Z"
    - latency: 2.217008ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:45:24Z"
    - latency: 774.334µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:44:24Z"
    - latency: 2.242269ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:44:24Z"
    - latency: 1.313409ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:43:24Z"
    - latency: 2.098248ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:43:24Z"
kind: List
metadata:
  resourceVersion: ""