apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:06:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-252-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-252.ec2.internal
      uid: 5d43dc6c-28ec-4e7f-95f7-b52d0ffccb2a
    resourceVersion: "24741"
    uid: 8cec1ee2-a8e0-4c77-905c-a350ef835876
  spec:
    sourcePod: network-check-source-685456655f-87k8x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:13:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.330863ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:13:57Z"
    - latency: 996.799µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:12:57Z"
    - latency: 1.598343ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:11:57Z"
    - latency: 1.402034ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:10:57Z"
    - latency: 1.326008ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:09:57Z"
    - latency: 1.071935ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:08:57Z"
    - latency: 1.064553ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:07:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:06:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-252-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-252.ec2.internal
      uid: 5d43dc6c-28ec-4e7f-95f7-b52d0ffccb2a
    resourceVersion: "23447"
    uid: ca946e49-9f2f-4446-a258-6f2c5bf9d497
  spec:
    sourcePod: network-check-source-685456655f-87k8x
    targetEndpoint: a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:12:57Z"
      message: 'load-balancer-api-external: tcp connection to a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.190314ms
      message: 'load-balancer-api-external: tcp connection to a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:12:57Z"
    - latency: 13.523315ms
      message: 'load-balancer-api-external: resolved host name a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:12:57Z"
    - latency: 4.399125ms
      message: 'load-balancer-api-external: tcp connection to a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:11:57Z"
    - latency: 6.696611ms
      message: 'load-balancer-api-external: resolved host name a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:11:57Z"
    - latency: 5.166225ms
      message: 'load-balancer-api-external: tcp connection to a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:10:57Z"
    - latency: 12.966001ms
      message: 'load-balancer-api-external: resolved host name a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:10:57Z"
    - latency: 4.559367ms
      message: 'load-balancer-api-external: tcp connection to a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:09:57Z"
    - latency: 15.099018ms
      message: 'load-balancer-api-external: resolved host name a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:09:57Z"
    - latency: 4.163005ms
      message: 'load-balancer-api-external: tcp connection to a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:08:57Z"
    - latency: 7.758666ms
      message: 'load-balancer-api-external: resolved host name a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:08:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:06:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-252-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-252.ec2.internal
      uid: 5d43dc6c-28ec-4e7f-95f7-b52d0ffccb2a
    resourceVersion: "23446"
    uid: d95fc718-27fe-420a-b9a3-a6a30d993346
  spec:
    sourcePod: network-check-source-685456655f-87k8x
    targetEndpoint: a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:12:57Z"
      message: 'load-balancer-api-internal: tcp connection to a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.310648ms
      message: 'load-balancer-api-internal: tcp connection to a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:12:57Z"
    - latency: 13.452646ms
      message: 'load-balancer-api-internal: resolved host name a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:12:57Z"
    - latency: 4.729376ms
      message: 'load-balancer-api-internal: tcp connection to a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:11:57Z"
    - latency: 6.625334ms
      message: 'load-balancer-api-internal: resolved host name a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:11:57Z"
    - latency: 5.182424ms
      message: 'load-balancer-api-internal: tcp connection to a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:10:57Z"
    - latency: 12.902498ms
      message: 'load-balancer-api-internal: resolved host name a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:10:57Z"
    - latency: 4.499437ms
      message: 'load-balancer-api-internal: tcp connection to a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:09:57Z"
    - latency: 15.007242ms
      message: 'load-balancer-api-internal: resolved host name a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:09:57Z"
    - latency: 3.651209ms
      message: 'load-balancer-api-internal: tcp connection to a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:08:57Z"
    - latency: 7.628647ms
      message: 'load-balancer-api-internal: resolved host name a3d6f95e340fd43238e33216c3440a84-98bcd7b6df5c7bb9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:08:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:06:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-252-to-network-check-target-ip-10-0-131-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-252.ec2.internal
      uid: 5d43dc6c-28ec-4e7f-95f7-b52d0ffccb2a
    resourceVersion: "24738"
    uid: 341282f3-85fa-4198-baba-2a33789f693e
  spec:
    sourcePod: network-check-source-685456655f-87k8x
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:13:57Z"
      message: 'network-check-target-ip-10-0-131-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.920295ms
      message: 'network-check-target-ip-10-0-131-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:13:57Z"
    - latency: 2.324102ms
      message: 'network-check-target-ip-10-0-131-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:12:57Z"
    - latency: 1.724858ms
      message: 'network-check-target-ip-10-0-131-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:11:57Z"
    - latency: 2.099358ms
      message: 'network-check-target-ip-10-0-131-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:10:57Z"
    - latency: 2.103845ms
      message: 'network-check-target-ip-10-0-131-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:09:57Z"
    - latency: 2.046223ms
      message: 'network-check-target-ip-10-0-131-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:08:57Z"
    - latency: 2.334655ms
      message: 'network-check-target-ip-10-0-131-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:07:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:06:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-252-to-network-check-target-ip-10-0-139-252
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-252.ec2.internal
      uid: 5d43dc6c-28ec-4e7f-95f7-b52d0ffccb2a
    resourceVersion: "24737"
    uid: 0156a77b-129d-4edf-a39b-6a7fda114e86
  spec:
    sourcePod: network-check-source-685456655f-87k8x
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:13:57Z"
      message: 'network-check-target-ip-10-0-139-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.192232ms
      message: 'network-check-target-ip-10-0-139-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:13:57Z"
    - latency: 1.486509ms
      message: 'network-check-target-ip-10-0-139-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:12:57Z"
    - latency: 792.485µs
      message: 'network-check-target-ip-10-0-139-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:11:57Z"
    - latency: 952.488µs
      message: 'network-check-target-ip-10-0-139-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:10:57Z"
    - latency: 1.106021ms
      message: 'network-check-target-ip-10-0-139-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:09:57Z"
    - latency: 950.443µs
      message: 'network-check-target-ip-10-0-139-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:08:57Z"
    - latency: 2.330713ms
      message: 'network-check-target-ip-10-0-139-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:07:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:06:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-252-to-network-check-target-ip-10-0-142-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-252.ec2.internal
      uid: 5d43dc6c-28ec-4e7f-95f7-b52d0ffccb2a
    resourceVersion: "24739"
    uid: 813865c5-e5d0-437a-a07b-1ed13f7fce95
  spec:
    sourcePod: network-check-source-685456655f-87k8x
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:13:57Z"
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.667914ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:13:57Z"
    - latency: 2.480876ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:12:57Z"
    - latency: 2.292729ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:11:57Z"
    - latency: 2.13435ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:10:57Z"
    - latency: 2.363135ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:09:57Z"
    - latency: 2.201236ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:08:57Z"
    - latency: 3.260955ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:07:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:06:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-252-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-252.ec2.internal
      uid: 5d43dc6c-28ec-4e7f-95f7-b52d0ffccb2a
    resourceVersion: "23445"
    uid: 46952f09-d2e2-421a-81e7-deababbdf699
  spec:
    sourcePod: network-check-source-685456655f-87k8x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:12:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 916.899µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:12:57Z"
    - latency: 2.255608ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:12:57Z"
    - latency: 747.05µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:11:57Z"
    - latency: 2.102187ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:11:57Z"
    - latency: 912.44µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:10:57Z"
    - latency: 2.502434ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:10:57Z"
    - latency: 959.87µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:09:57Z"
    - latency: 1.812767ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:09:57Z"
    - latency: 901.921µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:08:57Z"
    - latency: 2.372373ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:08:57Z"
kind: List
metadata:
  resourceVersion: ""