apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:59:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-30-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-30.ec2.internal
      uid: 5a5be222-620c-4a56-b2a3-b27c153214dd
    resourceVersion: "23549"
    uid: 63cc0d0d-c365-4110-b287-f0e8ff02633f
  spec:
    sourcePod: network-check-source-685456655f-bxbz7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T16:06:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.012141ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:06:12Z"
    - latency: 1.10455ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:05:12Z"
    - latency: 829.09µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:04:12Z"
    - latency: 1.027639ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:03:12Z"
    - latency: 1.486482ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:02:12Z"
    - latency: 1.334272ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:12Z"
    - latency: 1.013806ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:00:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:59:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-30-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-30.ec2.internal
      uid: 5a5be222-620c-4a56-b2a3-b27c153214dd
    resourceVersion: "22580"
    uid: 283aa887-b122-4f84-a734-4d28d5c6cdd8
  spec:
    sourcePod: network-check-source-685456655f-bxbz7
    targetEndpoint: a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T16:05:12Z"
      message: 'load-balancer-api-external: tcp connection to a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.916789ms
      message: 'load-balancer-api-external: tcp connection to a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:05:12Z"
    - latency: 7.205889ms
      message: 'load-balancer-api-external: resolved host name a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:05:12Z"
    - latency: 4.128527ms
      message: 'load-balancer-api-external: tcp connection to a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:04:12Z"
    - latency: 7.443113ms
      message: 'load-balancer-api-external: resolved host name a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:04:12Z"
    - latency: 4.047447ms
      message: 'load-balancer-api-external: tcp connection to a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:03:12Z"
    - latency: 8.907817ms
      message: 'load-balancer-api-external: resolved host name a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:03:12Z"
    - latency: 4.097543ms
      message: 'load-balancer-api-external: tcp connection to a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:02:12Z"
    - latency: 9.660343ms
      message: 'load-balancer-api-external: resolved host name a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:02:12Z"
    - latency: 6.208161ms
      message: 'load-balancer-api-external: tcp connection to a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:12Z"
    - latency: 14.666645ms
      message: 'load-balancer-api-external: resolved host name a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:01:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:59:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-30-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-30.ec2.internal
      uid: 5a5be222-620c-4a56-b2a3-b27c153214dd
    resourceVersion: "22581"
    uid: 6189ff21-0abf-4a4f-8603-8d0bc0e24923
  spec:
    sourcePod: network-check-source-685456655f-bxbz7
    targetEndpoint: a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T16:05:12Z"
      message: 'load-balancer-api-internal: tcp connection to a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.842925ms
      message: 'load-balancer-api-internal: tcp connection to a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:05:12Z"
    - latency: 7.160242ms
      message: 'load-balancer-api-internal: resolved host name a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:05:12Z"
    - latency: 4.135ms
      message: 'load-balancer-api-internal: tcp connection to a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:04:12Z"
    - latency: 7.369568ms
      message: 'load-balancer-api-internal: resolved host name a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:04:12Z"
    - latency: 5.76735ms
      message: 'load-balancer-api-internal: tcp connection to a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:03:12Z"
    - latency: 8.879126ms
      message: 'load-balancer-api-internal: resolved host name a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:03:12Z"
    - latency: 5.309694ms
      message: 'load-balancer-api-internal: tcp connection to a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:02:12Z"
    - latency: 9.600859ms
      message: 'load-balancer-api-internal: resolved host name a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:02:12Z"
    - latency: 6.194922ms
      message: 'load-balancer-api-internal: tcp connection to a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:12Z"
    - latency: 14.644285ms
      message: 'load-balancer-api-internal: resolved host name a44d30b0ec77a4a5185db0075679accc-a6146c73356ffdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:01:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:59:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-30-to-network-check-target-ip-10-0-129-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-30.ec2.internal
      uid: 5a5be222-620c-4a56-b2a3-b27c153214dd
    resourceVersion: "23548"
    uid: 87498d0e-603f-4478-80f8-57afc30462a1
  spec:
    sourcePod: network-check-source-685456655f-bxbz7
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T16:06:12Z"
      message: 'network-check-target-ip-10-0-129-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.044468ms
      message: 'network-check-target-ip-10-0-129-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:06:12Z"
    - latency: 2.679981ms
      message: 'network-check-target-ip-10-0-129-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:05:12Z"
    - latency: 2.152198ms
      message: 'network-check-target-ip-10-0-129-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:04:12Z"
    - latency: 2.318303ms
      message: 'network-check-target-ip-10-0-129-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:03:12Z"
    - latency: 2.445617ms
      message: 'network-check-target-ip-10-0-129-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:02:12Z"
    - latency: 3.155336ms
      message: 'network-check-target-ip-10-0-129-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:12Z"
    - latency: 2.700367ms
      message: 'network-check-target-ip-10-0-129-74: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:00:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:59:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-30-to-network-check-target-ip-10-0-130-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-30.ec2.internal
      uid: 5a5be222-620c-4a56-b2a3-b27c153214dd
    resourceVersion: "23546"
    uid: 7222ab1c-e14c-4c04-a4c1-77dbdfd93377
  spec:
    sourcePod: network-check-source-685456655f-bxbz7
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T16:06:12Z"
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.032013ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:06:12Z"
    - latency: 1.111823ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:05:12Z"
    - latency: 1.650771ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:04:12Z"
    - latency: 1.310933ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:03:12Z"
    - latency: 938.859µs
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:02:12Z"
    - latency: 1.551473ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:12Z"
    - latency: 1.494982ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:00:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:59:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-30-to-network-check-target-ip-10-0-131-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-30.ec2.internal
      uid: 5a5be222-620c-4a56-b2a3-b27c153214dd
    resourceVersion: "23547"
    uid: 675ffd0f-cd74-4202-98cc-f97780315bbe
  spec:
    sourcePod: network-check-source-685456655f-bxbz7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T16:06:12Z"
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.348038ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:06:12Z"
    - latency: 3.349213ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:05:12Z"
    - latency: 2.512526ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:04:12Z"
    - latency: 2.465359ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:03:12Z"
    - latency: 2.490711ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:02:12Z"
    - latency: 2.678715ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:12Z"
    - latency: 2.779006ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:00:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:59:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-30-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-30.ec2.internal
      uid: 5a5be222-620c-4a56-b2a3-b27c153214dd
    resourceVersion: "22578"
    uid: bb8e6216-f991-4956-ba55-f6ec0c6eeb0b
  spec:
    sourcePod: network-check-source-685456655f-bxbz7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T16:05:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 966.899µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:05:12Z"
    - latency: 2.277367ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:05:12Z"
    - latency: 827.262µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:04:12Z"
    - latency: 1.908039ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:04:12Z"
    - latency: 1.129194ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:03:12Z"
    - latency: 1.954646ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:03:12Z"
    - latency: 744.756µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:02:12Z"
    - latency: 2.362009ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:02:12Z"
    - latency: 1.790636ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:12Z"
    - latency: 1.938644ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:01:12Z"
kind: List
metadata:
  resourceVersion: ""