apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T02:56:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-247-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-247.ec2.internal
      uid: 97008513-5399-48eb-8105-7490c3405934
    resourceVersion: "14866"
    uid: 9d5c4fe4-0352-460b-8cff-54979b674c46
  spec:
    sourcePod: network-check-source-685456655f-hbkts
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T03:03:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.365354ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:03:13Z"
    - latency: 1.001513ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:02:13Z"
    - latency: 784.23µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:01:13Z"
    - latency: 936.442µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:00:13Z"
    - latency: 1.116409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:59:13Z"
    - latency: 946.07µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:58:13Z"
    - latency: 968.256µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:57:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T02:56:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-247-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-247.ec2.internal
      uid: 97008513-5399-48eb-8105-7490c3405934
    resourceVersion: "14534"
    uid: b7c1891d-dc91-4c1f-959f-2071d3105df8
  spec:
    sourcePod: network-check-source-685456655f-hbkts
    targetEndpoint: a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T03:02:13Z"
      message: 'load-balancer-api-external: tcp connection to a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.227892ms
      message: 'load-balancer-api-external: tcp connection to a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:02:13Z"
    - latency: 8.098652ms
      message: 'load-balancer-api-external: resolved host name a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T03:02:13Z"
    - latency: 4.653643ms
      message: 'load-balancer-api-external: tcp connection to a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:01:13Z"
    - latency: 10.902668ms
      message: 'load-balancer-api-external: resolved host name a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T03:01:13Z"
    - latency: 4.789683ms
      message: 'load-balancer-api-external: tcp connection to a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:00:13Z"
    - latency: 8.468032ms
      message: 'load-balancer-api-external: resolved host name a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T03:00:13Z"
    - latency: 5.489934ms
      message: 'load-balancer-api-external: tcp connection to a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:59:13Z"
    - latency: 6.973304ms
      message: 'load-balancer-api-external: resolved host name a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:59:13Z"
    - latency: 4.742622ms
      message: 'load-balancer-api-external: tcp connection to a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:58:13Z"
    - latency: 7.243009ms
      message: 'load-balancer-api-external: resolved host name a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:58:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T02:56:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-247-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-247.ec2.internal
      uid: 97008513-5399-48eb-8105-7490c3405934
    resourceVersion: "14535"
    uid: 6eb1fc81-631b-4ddd-b5e5-c64dba94f4f5
  spec:
    sourcePod: network-check-source-685456655f-hbkts
    targetEndpoint: a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T03:02:13Z"
      message: 'load-balancer-api-internal: tcp connection to a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.171231ms
      message: 'load-balancer-api-internal: tcp connection to a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:02:13Z"
    - latency: 8.144517ms
      message: 'load-balancer-api-internal: resolved host name a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T03:02:13Z"
    - latency: 4.64239ms
      message: 'load-balancer-api-internal: tcp connection to a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:01:13Z"
    - latency: 10.936833ms
      message: 'load-balancer-api-internal: resolved host name a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T03:01:13Z"
    - latency: 4.238352ms
      message: 'load-balancer-api-internal: tcp connection to a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:00:13Z"
    - latency: 8.613072ms
      message: 'load-balancer-api-internal: resolved host name a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T03:00:13Z"
    - latency: 5.396532ms
      message: 'load-balancer-api-internal: tcp connection to a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:59:13Z"
    - latency: 7.019425ms
      message: 'load-balancer-api-internal: resolved host name a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:59:13Z"
    - latency: 4.758177ms
      message: 'load-balancer-api-internal: tcp connection to a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:58:13Z"
    - latency: 7.342616ms
      message: 'load-balancer-api-internal: resolved host name a9a2edd1c02b748a4ad0c5997fb4b3ef-201533e127216f88.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:58:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T02:56:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-247-to-network-check-target-ip-10-0-131-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-247.ec2.internal
      uid: 97008513-5399-48eb-8105-7490c3405934
    resourceVersion: "14864"
    uid: 23643e9b-27a5-4c73-9b34-8082667fd387
  spec:
    sourcePod: network-check-source-685456655f-hbkts
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T03:03:13Z"
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.351825ms
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:03:13Z"
    - latency: 3.048459ms
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:02:13Z"
    - latency: 1.811857ms
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:01:13Z"
    - latency: 2.865823ms
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:00:13Z"
    - latency: 2.243353ms
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:59:13Z"
    - latency: 5.592516ms
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:58:13Z"
    - latency: 2.218951ms
      message: 'network-check-target-ip-10-0-131-102: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:57:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T02:56:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-247-to-network-check-target-ip-10-0-132-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-247.ec2.internal
      uid: 97008513-5399-48eb-8105-7490c3405934
    resourceVersion: "14863"
    uid: 3d5a4a90-17e8-4560-b42b-9952f4682b58
  spec:
    sourcePod: network-check-source-685456655f-hbkts
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T03:03:13Z"
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.293113ms
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:03:13Z"
    - latency: 890.152µs
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:02:13Z"
    - latency: 1.156763ms
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:01:13Z"
    - latency: 1.358492ms
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:00:13Z"
    - latency: 1.420523ms
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:59:13Z"
    - latency: 909.231µs
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:58:13Z"
    - latency: 1.677265ms
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:57:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T02:56:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-247-to-network-check-target-ip-10-0-141-131
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-247.ec2.internal
      uid: 97008513-5399-48eb-8105-7490c3405934
    resourceVersion: "14865"
    uid: f696d4bf-6cb9-4550-aac7-14b49b105ef7
  spec:
    sourcePod: network-check-source-685456655f-hbkts
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T03:03:13Z"
      message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.232103ms
      message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:03:13Z"
    - latency: 2.133442ms
      message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:02:13Z"
    - latency: 2.204482ms
      message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:01:13Z"
    - latency: 2.959717ms
      message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:00:13Z"
    - latency: 2.279398ms
      message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:59:13Z"
    - latency: 2.2228ms
      message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:58:13Z"
    - latency: 2.288039ms
      message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:57:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T02:56:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-247-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-247.ec2.internal
      uid: 97008513-5399-48eb-8105-7490c3405934
    resourceVersion: "14533"
    uid: f8fa661b-6e9e-4356-bfec-5e04dc383b87
  spec:
    sourcePod: network-check-source-685456655f-hbkts
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T03:02:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 789.977µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:02:13Z"
    - latency: 2.021636ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T03:02:13Z"
    - latency: 985.06µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:01:13Z"
    - latency: 1.69353ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T03:01:13Z"
    - latency: 969.145µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T03:00:13Z"
    - latency: 2.034404ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T03:00:13Z"
    - latency: 857.154µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:59:13Z"
    - latency: 1.667586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:59:13Z"
    - latency: 784.008µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T02:58:13Z"
    - latency: 2.29273ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T02:58:13Z"
kind: List
metadata:
  resourceVersion: ""