apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-03T14:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-58-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-58.ec2.internal
      uid: 85c78801-4282-4799-b84d-8dffce5d98c3
    resourceVersion: "15180"
    uid: a8b54fc7-e751-4b05-85ac-e1eaba82126c
  spec:
    sourcePod: network-check-source-65bdbbff45-r5zs9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-03T15:02:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.141843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:02:34Z"
    - latency: 1.228158ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:01:34Z"
    - latency: 1.302302ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:00:34Z"
    - latency: 815.575µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:59:34Z"
    - latency: 1.412ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:58:34Z"
    - latency: 994.632µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:57:34Z"
    - latency: 975.316µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:56:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-03T14:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-58-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-58.ec2.internal
      uid: 85c78801-4282-4799-b84d-8dffce5d98c3
    resourceVersion: "14675"
    uid: bda26318-872e-49f8-9bef-3fc8b86ffbbf
  spec:
    sourcePod: network-check-source-65bdbbff45-r5zs9
    targetEndpoint: a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-03T15:01:34Z"
      message: 'load-balancer-api-external: tcp connection to a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.363178ms
      message: 'load-balancer-api-external: tcp connection to a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:01:34Z"
    - latency: 7.846266ms
      message: 'load-balancer-api-external: resolved host name a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-03T15:01:34Z"
    - latency: 4.583894ms
      message: 'load-balancer-api-external: tcp connection to a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:00:34Z"
    - latency: 7.039858ms
      message: 'load-balancer-api-external: resolved host name a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-03T15:00:34Z"
    - latency: 4.989005ms
      message: 'load-balancer-api-external: tcp connection to a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:59:34Z"
    - latency: 8.46261ms
      message: 'load-balancer-api-external: resolved host name a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-03T14:59:34Z"
    - latency: 4.791692ms
      message: 'load-balancer-api-external: tcp connection to a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:58:34Z"
    - latency: 11.196518ms
      message: 'load-balancer-api-external: resolved host name a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-03T14:58:34Z"
    - latency: 4.109033ms
      message: 'load-balancer-api-external: tcp connection to a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:57:34Z"
    - latency: 6.608933ms
      message: 'load-balancer-api-external: resolved host name a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-03T14:57:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-03T14:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-58-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-58.ec2.internal
      uid: 85c78801-4282-4799-b84d-8dffce5d98c3
    resourceVersion: "14676"
    uid: 8d9ccae8-da13-42cc-a6cb-e4f5af1d1484
  spec:
    sourcePod: network-check-source-65bdbbff45-r5zs9
    targetEndpoint: a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-03T15:01:34Z"
      message: 'load-balancer-api-internal: tcp connection to a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.42151ms
      message: 'load-balancer-api-internal: tcp connection to a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:01:34Z"
    - latency: 7.789619ms
      message: 'load-balancer-api-internal: resolved host name a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-03T15:01:34Z"
    - latency: 4.941334ms
      message: 'load-balancer-api-internal: tcp connection to a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:00:34Z"
    - latency: 7.113028ms
      message: 'load-balancer-api-internal: resolved host name a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-03T15:00:34Z"
    - latency: 4.922222ms
      message: 'load-balancer-api-internal: tcp connection to a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:59:34Z"
    - latency: 8.51557ms
      message: 'load-balancer-api-internal: resolved host name a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-03T14:59:34Z"
    - latency: 4.912678ms
      message: 'load-balancer-api-internal: tcp connection to a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:58:34Z"
    - latency: 11.102696ms
      message: 'load-balancer-api-internal: resolved host name a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-03T14:58:34Z"
    - latency: 4.48792ms
      message: 'load-balancer-api-internal: tcp connection to a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:57:34Z"
    - latency: 6.674948ms
      message: 'load-balancer-api-internal: resolved host name a3bcf24b7fac4496cbb1d09e2bfdfc84-63084a6d3a987b7b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-03T14:57:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-03T14:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-58-to-network-check-target-ip-10-0-130-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-58.ec2.internal
      uid: 85c78801-4282-4799-b84d-8dffce5d98c3
    resourceVersion: "15178"
    uid: 61f0f55c-435e-42de-85a8-76d71d7e0efa
  spec:
    sourcePod: network-check-source-65bdbbff45-r5zs9
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-03T15:02:34Z"
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.226382ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:02:34Z"
    - latency: 2.604839ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:01:34Z"
    - latency: 2.350831ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:00:34Z"
    - latency: 2.11739ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:59:34Z"
    - latency: 2.389357ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:58:34Z"
    - latency: 2.502419ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:57:34Z"
    - latency: 2.622589ms
      message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:56:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-03T14:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-58-to-network-check-target-ip-10-0-133-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-58.ec2.internal
      uid: 85c78801-4282-4799-b84d-8dffce5d98c3
    resourceVersion: "15177"
    uid: 30caf658-f126-474f-a6c2-d41f88da0add
  spec:
    sourcePod: network-check-source-65bdbbff45-r5zs9
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-03T15:02:34Z"
      message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.405633ms
      message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:02:34Z"
    - latency: 881.112µs
      message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:01:34Z"
    - latency: 999.968µs
      message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:00:34Z"
    - latency: 751.481µs
      message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:59:34Z"
    - latency: 1.004107ms
      message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:58:34Z"
    - latency: 1.030199ms
      message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:57:34Z"
    - latency: 1.151508ms
      message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:56:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-03T14:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-58-to-network-check-target-ip-10-0-137-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-58.ec2.internal
      uid: 85c78801-4282-4799-b84d-8dffce5d98c3
    resourceVersion: "15179"
    uid: 3a8ac76f-dc02-4a3b-a79a-d0b3555ac52b
  spec:
    sourcePod: network-check-source-65bdbbff45-r5zs9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-03T15:02:34Z"
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.355323ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:02:34Z"
    - latency: 2.504612ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:01:34Z"
    - latency: 2.441102ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:00:34Z"
    - latency: 2.098307ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:59:34Z"
    - latency: 2.205286ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:58:34Z"
    - latency: 2.239838ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:57:34Z"
    - latency: 2.502855ms
      message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:56:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-03T14:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-58-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-58.ec2.internal
      uid: 85c78801-4282-4799-b84d-8dffce5d98c3
    resourceVersion: "14674"
    uid: 9a49869f-8f70-47da-b0ab-84426d501154
  spec:
    sourcePod: network-check-source-65bdbbff45-r5zs9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-03T15:01:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 910.632µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:01:34Z"
    - latency: 1.69696ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-03T15:01:34Z"
    - latency: 1.016696ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T15:00:34Z"
    - latency: 1.747179ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-03T15:00:34Z"
    - latency: 1.156084ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:59:34Z"
    - latency: 1.579615ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-03T14:59:34Z"
    - latency: 810.677µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:58:34Z"
    - latency: 1.730261ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-03T14:58:34Z"
    - latency: 892.52µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-03T14:57:34Z"
    - latency: 1.675523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-03T14:57:34Z"
kind: List
metadata:
  resourceVersion: ""