apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T04:03:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-231-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-231.ec2.internal
      uid: 18d4862b-72ca-47ae-b5a2-0ec1db4fdd49
    resourceVersion: "24351"
    uid: d784746e-cc27-4756-8ec7-ad6dcfa7cf1d
  spec:
    sourcePod: network-check-source-685456655f-6qlcn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T04:10:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 912.047µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:10:18Z"
    - latency: 1.215723ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:09:18Z"
    - latency: 946.062µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:08:18Z"
    - latency: 971.812µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:07:18Z"
    - latency: 1.068406ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:06:18Z"
    - latency: 1.04843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:05:18Z"
    - latency: 1.196012ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:04:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T04:03:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-231-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-231.ec2.internal
      uid: 18d4862b-72ca-47ae-b5a2-0ec1db4fdd49
    resourceVersion: "27545"
    uid: 3e29d612-e4b3-4067-9b27-0dd66877f23a
  spec:
    sourcePod: network-check-source-685456655f-6qlcn
    targetEndpoint: a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T04:09:18Z"
      message: 'load-balancer-api-external: tcp connection to a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.609939ms
      message: 'load-balancer-api-external: tcp connection to a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:15:18Z"
    - latency: 6.51688ms
      message: 'load-balancer-api-external: resolved host name a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:15:18Z"
    - latency: 3.395268ms
      message: 'load-balancer-api-external: tcp connection to a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:14:18Z"
    - latency: 7.766193ms
      message: 'load-balancer-api-external: resolved host name a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:14:18Z"
    - latency: 3.410264ms
      message: 'load-balancer-api-external: tcp connection to a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:13:18Z"
    - latency: 6.402729ms
      message: 'load-balancer-api-external: resolved host name a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:13:18Z"
    - latency: 3.241914ms
      message: 'load-balancer-api-external: tcp connection to a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:12:18Z"
    - latency: 6.588351ms
      message: 'load-balancer-api-external: resolved host name a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:12:18Z"
    - latency: 4.989417ms
      message: 'load-balancer-api-external: tcp connection to a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:11:18Z"
    - latency: 7.136951ms
      message: 'load-balancer-api-external: resolved host name a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:11:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T04:03:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-231-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-231.ec2.internal
      uid: 18d4862b-72ca-47ae-b5a2-0ec1db4fdd49
    resourceVersion: "27544"
    uid: 7e0293ee-918b-49db-b7ac-2f25a4c5adc9
  spec:
    sourcePod: network-check-source-685456655f-6qlcn
    targetEndpoint: a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T04:09:18Z"
      message: 'load-balancer-api-internal: tcp connection to a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.139581ms
      message: 'load-balancer-api-internal: tcp connection to a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:15:18Z"
    - latency: 6.477672ms
      message: 'load-balancer-api-internal: resolved host name a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:15:18Z"
    - latency: 3.420699ms
      message: 'load-balancer-api-internal: tcp connection to a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:14:18Z"
    - latency: 7.883437ms
      message: 'load-balancer-api-internal: resolved host name a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:14:18Z"
    - latency: 3.364782ms
      message: 'load-balancer-api-internal: tcp connection to a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:13:18Z"
    - latency: 6.420877ms
      message: 'load-balancer-api-internal: resolved host name a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:13:18Z"
    - latency: 3.29291ms
      message: 'load-balancer-api-internal: tcp connection to a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:12:18Z"
    - latency: 6.658331ms
      message: 'load-balancer-api-internal: resolved host name a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:12:18Z"
    - latency: 5.039129ms
      message: 'load-balancer-api-internal: tcp connection to a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:11:18Z"
    - latency: 7.217014ms
      message: 'load-balancer-api-internal: resolved host name a07a90dfa9316439889b8fb2de7c21e0-76e7b7bda4348229.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:11:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T04:03:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-231-to-network-check-target-ip-10-0-128-141
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-231.ec2.internal
      uid: 18d4862b-72ca-47ae-b5a2-0ec1db4fdd49
    resourceVersion: "24349"
    uid: 237535e5-5d7d-472c-b553-7a779b1227b8
  spec:
    sourcePod: network-check-source-685456655f-6qlcn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T04:10:18Z"
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.433442ms
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:10:18Z"
    - latency: 2.54417ms
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:09:18Z"
    - latency: 2.416179ms
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:08:18Z"
    - latency: 2.956079ms
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:07:18Z"
    - latency: 2.354959ms
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:06:18Z"
    - latency: 2.727641ms
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:05:18Z"
    - latency: 2.715787ms
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:04:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T04:03:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-231-to-network-check-target-ip-10-0-128-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-231.ec2.internal
      uid: 18d4862b-72ca-47ae-b5a2-0ec1db4fdd49
    resourceVersion: "24350"
    uid: 9412623f-f8b8-4cbe-b144-029e30906ba5
  spec:
    sourcePod: network-check-source-685456655f-6qlcn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T04:10:18Z"
      message: 'network-check-target-ip-10-0-128-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.441131ms
      message: 'network-check-target-ip-10-0-128-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:10:18Z"
    - latency: 2.467053ms
      message: 'network-check-target-ip-10-0-128-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:09:18Z"
    - latency: 2.813216ms
      message: 'network-check-target-ip-10-0-128-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:08:18Z"
    - latency: 2.211683ms
      message: 'network-check-target-ip-10-0-128-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:07:18Z"
    - latency: 2.168504ms
      message: 'network-check-target-ip-10-0-128-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:06:18Z"
    - latency: 2.380605ms
      message: 'network-check-target-ip-10-0-128-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:05:18Z"
    - latency: 2.993737ms
      message: 'network-check-target-ip-10-0-128-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:04:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T04:03:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-231-to-network-check-target-ip-10-0-131-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-231.ec2.internal
      uid: 18d4862b-72ca-47ae-b5a2-0ec1db4fdd49
    resourceVersion: "24348"
    uid: 9cd04c72-f352-4568-aba2-62117ee81060
  spec:
    sourcePod: network-check-source-685456655f-6qlcn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T04:10:18Z"
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 810.812µs
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:10:18Z"
    - latency: 983.787µs
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:09:18Z"
    - latency: 1.404155ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:08:18Z"
    - latency: 1.415806ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:07:18Z"
    - latency: 989.513µs
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:06:18Z"
    - latency: 1.541058ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:05:18Z"
    - latency: 1.781176ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:04:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T04:03:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-231-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-231.ec2.internal
      uid: 18d4862b-72ca-47ae-b5a2-0ec1db4fdd49
    resourceVersion: "27543"
    uid: aa433f8a-bac0-43f5-9441-b36d051ef75d
  spec:
    sourcePod: network-check-source-685456655f-6qlcn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T04:09:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.138893ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:15:18Z"
    - latency: 2.139546ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:15:18Z"
    - latency: 949.712µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:14:18Z"
    - latency: 1.893734ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:14:18Z"
    - latency: 1.141551ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:13:18Z"
    - latency: 1.681696ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:13:18Z"
    - latency: 834.996µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:12:18Z"
    - latency: 1.793421ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:12:18Z"
    - latency: 806.101µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T04:11:18Z"
    - latency: 1.905203ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T04:11:18Z"
kind: List
metadata:
  resourceVersion: ""