apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T08:01:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-97-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-97.ec2.internal
      uid: 910f07be-7ecb-44b5-9602-572688717474
    resourceVersion: "12317"
    uid: 48684dab-e35b-4893-abed-b6af7b894536
  spec:
    sourcePod: network-check-source-6f78d59f99-clkjm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T08:09:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.039ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:00Z"
    - latency: 1.08839ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:00Z"
    - latency: 1.059178ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:00Z"
    - latency: 963.134µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:00Z"
    - latency: 1.260316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:00Z"
    - latency: 1.084063ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:04:00Z"
    - latency: 1.178774ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:03:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T08:01:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-97-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-97.ec2.internal
      uid: 910f07be-7ecb-44b5-9602-572688717474
    resourceVersion: "12015"
    uid: f0c9c3b0-7700-4644-80a0-8f4114610636
  spec:
    sourcePod: network-check-source-6f78d59f99-clkjm
    targetEndpoint: a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T08:08:00Z"
      message: 'load-balancer-api-external: tcp connection to a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.851122ms
      message: 'load-balancer-api-external: tcp connection to a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:00Z"
    - latency: 8.247068ms
      message: 'load-balancer-api-external: resolved host name a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:08:00Z"
    - latency: 16.480154ms
      message: 'load-balancer-api-external: tcp connection to a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:00Z"
    - latency: 8.252407ms
      message: 'load-balancer-api-external: resolved host name a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:07:00Z"
    - latency: 17.031226ms
      message: 'load-balancer-api-external: tcp connection to a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:00Z"
    - latency: 7.802759ms
      message: 'load-balancer-api-external: resolved host name a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:06:00Z"
    - latency: 16.442543ms
      message: 'load-balancer-api-external: tcp connection to a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:00Z"
    - latency: 9.316688ms
      message: 'load-balancer-api-external: resolved host name a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:05:00Z"
    - latency: 18.500034ms
      message: 'load-balancer-api-external: tcp connection to a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:04:00Z"
    - latency: 11.925843ms
      message: 'load-balancer-api-external: resolved host name a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:04:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T08:01:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-97-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-97.ec2.internal
      uid: 910f07be-7ecb-44b5-9602-572688717474
    resourceVersion: "12014"
    uid: c06b614f-af1f-4668-8362-178b20d84a5c
  spec:
    sourcePod: network-check-source-6f78d59f99-clkjm
    targetEndpoint: a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T08:08:00Z"
      message: 'load-balancer-api-internal: tcp connection to a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.776196ms
      message: 'load-balancer-api-internal: tcp connection to a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:00Z"
    - latency: 8.187942ms
      message: 'load-balancer-api-internal: resolved host name a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:08:00Z"
    - latency: 16.201538ms
      message: 'load-balancer-api-internal: tcp connection to a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:00Z"
    - latency: 8.222469ms
      message: 'load-balancer-api-internal: resolved host name a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:07:00Z"
    - latency: 13.558758ms
      message: 'load-balancer-api-internal: tcp connection to a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:00Z"
    - latency: 7.776088ms
      message: 'load-balancer-api-internal: resolved host name a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:06:00Z"
    - latency: 16.441828ms
      message: 'load-balancer-api-internal: tcp connection to a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:00Z"
    - latency: 9.277592ms
      message: 'load-balancer-api-internal: resolved host name a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:05:00Z"
    - latency: 18.521173ms
      message: 'load-balancer-api-internal: tcp connection to a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:04:00Z"
    - latency: 11.873138ms
      message: 'load-balancer-api-internal: resolved host name a72cb65e53cad4bdb911e5073975148d-0ddf2a3cd645c81c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:04:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T08:01:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-97-to-network-check-target-ip-10-0-131-97
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-97.ec2.internal
      uid: 910f07be-7ecb-44b5-9602-572688717474
    resourceVersion: "12314"
    uid: 3ddb9c73-75e1-4384-a0be-0bb102591ee1
  spec:
    sourcePod: network-check-source-6f78d59f99-clkjm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T08:09:00Z"
      message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 938.542µs
      message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:00Z"
    - latency: 857.813µs
      message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:00Z"
    - latency: 923.903µs
      message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:00Z"
    - latency: 781.559µs
      message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:00Z"
    - latency: 1.345357ms
      message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:00Z"
    - latency: 1.201362ms
      message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:04:00Z"
    - latency: 1.22668ms
      message: 'network-check-target-ip-10-0-131-97: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:03:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T08:01:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-97-to-network-check-target-ip-10-0-133-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-97.ec2.internal
      uid: 910f07be-7ecb-44b5-9602-572688717474
    resourceVersion: "12315"
    uid: 9e3a8c8c-ef79-495c-8f5b-eb56b988e560
  spec:
    sourcePod: network-check-source-6f78d59f99-clkjm
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T08:09:00Z"
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.814221ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:00Z"
    - latency: 2.162022ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:00Z"
    - latency: 1.839668ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:00Z"
    - latency: 1.932467ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:00Z"
    - latency: 1.692023ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:00Z"
    - latency: 2.237007ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:04:00Z"
    - latency: 2.322251ms
      message: 'network-check-target-ip-10-0-133-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:03:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T08:01:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-97-to-network-check-target-ip-10-0-143-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-97.ec2.internal
      uid: 910f07be-7ecb-44b5-9602-572688717474
    resourceVersion: "12316"
    uid: 1ad04ab9-8a2d-4867-948a-835a977065d3
  spec:
    sourcePod: network-check-source-6f78d59f99-clkjm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T08:09:00Z"
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.400228ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:00Z"
    - latency: 2.368513ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:00Z"
    - latency: 2.210974ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:00Z"
    - latency: 2.166737ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:00Z"
    - latency: 2.431829ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:00Z"
    - latency: 5.612928ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:04:00Z"
    - latency: 2.565932ms
      message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:03:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T08:01:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-97-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-97.ec2.internal
      uid: 910f07be-7ecb-44b5-9602-572688717474
    resourceVersion: "12013"
    uid: 003bb11a-af84-4fe3-99a8-16fdf49e3413
  spec:
    sourcePod: network-check-source-6f78d59f99-clkjm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T08:08:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.237µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:00Z"
    - latency: 1.70309ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:08:00Z"
    - latency: 876.706µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:00Z"
    - latency: 2.169791ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:07:00Z"
    - latency: 1.082276ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:00Z"
    - latency: 1.619974ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:06:00Z"
    - latency: 863.696µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:00Z"
    - latency: 2.400564ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:05:00Z"
    - latency: 4.571821ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:04:00Z"
    - latency: 1.731247ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:04:00Z"
kind: List
metadata:
  resourceVersion: ""