apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T03:11:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-92-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-92.ec2.internal
      uid: 47deb834-a0cf-4843-955f-00822250d515
    resourceVersion: "14417"
    uid: 2f8c302d-4639-41ec-81eb-0ebc63489e69
  spec:
    sourcePod: network-check-source-685456655f-fwsnl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T03:18:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 934.303µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:18:56Z"
    - latency: 1.191968ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:17:56Z"
    - latency: 864.46µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:16:56Z"
    - latency: 907.508µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:15:56Z"
    - latency: 841.236µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:14:56Z"
    - latency: 1.304972ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:13:56Z"
    - latency: 1.023518ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:12:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T03:11:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-92-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-92.ec2.internal
      uid: 47deb834-a0cf-4843-955f-00822250d515
    resourceVersion: "14087"
    uid: bf671df6-ca06-4fbd-9f9e-31e3eeb4bcfa
  spec:
    sourcePod: network-check-source-685456655f-fwsnl
    targetEndpoint: a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T03:17:56Z"
      message: 'load-balancer-api-external: tcp connection to a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.82584ms
      message: 'load-balancer-api-external: tcp connection to a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:17:56Z"
    - latency: 7.803361ms
      message: 'load-balancer-api-external: resolved host name a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:17:56Z"
    - latency: 4.90523ms
      message: 'load-balancer-api-external: tcp connection to a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:16:56Z"
    - latency: 8.859055ms
      message: 'load-balancer-api-external: resolved host name a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:16:56Z"
    - latency: 5.090418ms
      message: 'load-balancer-api-external: tcp connection to a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:15:56Z"
    - latency: 9.493177ms
      message: 'load-balancer-api-external: resolved host name a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:15:56Z"
    - latency: 5.002386ms
      message: 'load-balancer-api-external: tcp connection to a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:14:56Z"
    - latency: 7.726028ms
      message: 'load-balancer-api-external: resolved host name a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:14:56Z"
    - latency: 4.253751ms
      message: 'load-balancer-api-external: tcp connection to a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:13:56Z"
    - latency: 7.661548ms
      message: 'load-balancer-api-external: resolved host name a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:13:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T03:11:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-92-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-92.ec2.internal
      uid: 47deb834-a0cf-4843-955f-00822250d515
    resourceVersion: "14086"
    uid: efb33f85-9b4a-412b-bea6-775f6e7b8d74
  spec:
    sourcePod: network-check-source-685456655f-fwsnl
    targetEndpoint: a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T03:17:56Z"
      message: 'load-balancer-api-internal: tcp connection to a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.816123ms
      message: 'load-balancer-api-internal: tcp connection to a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:17:56Z"
    - latency: 8.019508ms
      message: 'load-balancer-api-internal: resolved host name a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:17:56Z"
    - latency: 4.88605ms
      message: 'load-balancer-api-internal: tcp connection to a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:16:56Z"
    - latency: 8.99122ms
      message: 'load-balancer-api-internal: resolved host name a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:16:56Z"
    - latency: 4.936521ms
      message: 'load-balancer-api-internal: tcp connection to a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:15:56Z"
    - latency: 9.529119ms
      message: 'load-balancer-api-internal: resolved host name a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:15:56Z"
    - latency: 4.847446ms
      message: 'load-balancer-api-internal: tcp connection to a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:14:56Z"
    - latency: 7.858087ms
      message: 'load-balancer-api-internal: resolved host name a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:14:56Z"
    - latency: 4.228869ms
      message: 'load-balancer-api-internal: tcp connection to a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:13:56Z"
    - latency: 7.755112ms
      message: 'load-balancer-api-internal: resolved host name a7c4ce6c361104bf3806d891fc7394d3-bb7e2528b0b11c65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:13:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T03:11:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-92-to-network-check-target-ip-10-0-139-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-92.ec2.internal
      uid: 47deb834-a0cf-4843-955f-00822250d515
    resourceVersion: "14415"
    uid: 5d35eb74-f86f-4de5-a913-872a7519e9ec
  spec:
    sourcePod: network-check-source-685456655f-fwsnl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T03:18:56Z"
      message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.649081ms
      message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:18:56Z"
    - latency: 2.033045ms
      message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:17:56Z"
    - latency: 1.751636ms
      message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:16:56Z"
    - latency: 1.537557ms
      message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:15:56Z"
    - latency: 1.765349ms
      message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:14:56Z"
    - latency: 1.872961ms
      message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:13:56Z"
    - latency: 1.789886ms
      message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:12:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T03:11:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-92-to-network-check-target-ip-10-0-142-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-92.ec2.internal
      uid: 47deb834-a0cf-4843-955f-00822250d515
    resourceVersion: "14416"
    uid: 7cd14eb0-0f94-47c7-a8d5-7fbcf5bfee31
  spec:
    sourcePod: network-check-source-685456655f-fwsnl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T03:18:56Z"
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.913502ms
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:18:56Z"
    - latency: 2.097199ms
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:17:56Z"
    - latency: 1.89227ms
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:16:56Z"
    - latency: 2.064383ms
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:15:56Z"
    - latency: 1.927531ms
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:14:56Z"
    - latency: 2.247679ms
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:13:56Z"
    - latency: 2.114703ms
      message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:12:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T03:11:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-92-to-network-check-target-ip-10-0-142-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-92.ec2.internal
      uid: 47deb834-a0cf-4843-955f-00822250d515
    resourceVersion: "14414"
    uid: 07d64138-7e4a-45f6-add4-b4a922780c7f
  spec:
    sourcePod: network-check-source-685456655f-fwsnl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T03:18:56Z"
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 785.394µs
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:18:56Z"
    - latency: 1.39982ms
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:17:56Z"
    - latency: 880.831µs
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:16:56Z"
    - latency: 1.032742ms
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:15:56Z"
    - latency: 1.070605ms
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:14:56Z"
    - latency: 900.877µs
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:13:56Z"
    - latency: 2.041048ms
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:12:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T03:11:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-92-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-92.ec2.internal
      uid: 47deb834-a0cf-4843-955f-00822250d515
    resourceVersion: "14085"
    uid: ab62de77-5011-4b69-8681-965f2e25e3c7
  spec:
    sourcePod: network-check-source-685456655f-fwsnl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T03:17:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 936.778µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:17:56Z"
    - latency: 1.825595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:17:56Z"
    - latency: 1.00492ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:16:56Z"
    - latency: 1.764941ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:16:56Z"
    - latency: 741.791µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:15:56Z"
    - latency: 2.223752ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:15:56Z"
    - latency: 841.505µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:14:56Z"
    - latency: 2.033695ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:14:56Z"
    - latency: 841.589µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:13:56Z"
    - latency: 1.647228ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:13:56Z"
kind: List
metadata:
  resourceVersion: ""