apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T02:45:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-170-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-170.ec2.internal
      uid: cdd183e8-8de5-46c5-b2ca-fd27fd9265f3
    resourceVersion: "24154"
    uid: 88343031-1ce5-4d1c-a231-9cffc78894af
  spec:
    sourcePod: network-check-source-8894fc9bd-crw5h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T02:52:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.459111ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:52:53Z"
    - latency: 1.151514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:51:53Z"
    - latency: 911.285µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:50:53Z"
    - latency: 871.882µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:49:53Z"
    - latency: 839.501µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:48:53Z"
    - latency: 901.683µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:47:53Z"
    - latency: 973.94µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:46:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T02:45:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-170-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-170.ec2.internal
      uid: cdd183e8-8de5-46c5-b2ca-fd27fd9265f3
    resourceVersion: "23014"
    uid: 7e61b227-45bc-4f22-8ebe-06a81080079a
  spec:
    sourcePod: network-check-source-8894fc9bd-crw5h
    targetEndpoint: a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T02:51:53Z"
      message: 'load-balancer-api-external: tcp connection to a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.562807ms
      message: 'load-balancer-api-external: tcp connection to a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:51:53Z"
    - latency: 7.823034ms
      message: 'load-balancer-api-external: resolved host name a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T02:51:53Z"
    - latency: 3.525601ms
      message: 'load-balancer-api-external: tcp connection to a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:50:53Z"
    - latency: 7.886913ms
      message: 'load-balancer-api-external: resolved host name a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T02:50:53Z"
    - latency: 4.401087ms
      message: 'load-balancer-api-external: tcp connection to a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:49:53Z"
    - latency: 8.192232ms
      message: 'load-balancer-api-external: resolved host name a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T02:49:53Z"
    - latency: 4.657515ms
      message: 'load-balancer-api-external: tcp connection to a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:48:53Z"
    - latency: 6.85518ms
      message: 'load-balancer-api-external: resolved host name a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T02:48:53Z"
    - latency: 4.82138ms
      message: 'load-balancer-api-external: tcp connection to a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:47:53Z"
    - latency: 8.661948ms
      message: 'load-balancer-api-external: resolved host name a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T02:47:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T02:45:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-170-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-170.ec2.internal
      uid: cdd183e8-8de5-46c5-b2ca-fd27fd9265f3
    resourceVersion: "23013"
    uid: 435ba738-b22c-4d7a-9ec0-87d44ae3ceae
  spec:
    sourcePod: network-check-source-8894fc9bd-crw5h
    targetEndpoint: a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T02:51:53Z"
      message: 'load-balancer-api-internal: tcp connection to a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.478635ms
      message: 'load-balancer-api-internal: tcp connection to a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:51:53Z"
    - latency: 7.846017ms
      message: 'load-balancer-api-internal: resolved host name a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T02:51:53Z"
    - latency: 5.333ms
      message: 'load-balancer-api-internal: tcp connection to a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:50:53Z"
    - latency: 7.869291ms
      message: 'load-balancer-api-internal: resolved host name a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T02:50:53Z"
    - latency: 4.297101ms
      message: 'load-balancer-api-internal: tcp connection to a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:49:53Z"
    - latency: 8.273974ms
      message: 'load-balancer-api-internal: resolved host name a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T02:49:53Z"
    - latency: 5.734572ms
      message: 'load-balancer-api-internal: tcp connection to a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:48:53Z"
    - latency: 6.867508ms
      message: 'load-balancer-api-internal: resolved host name a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T02:48:53Z"
    - latency: 4.852555ms
      message: 'load-balancer-api-internal: tcp connection to a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:47:53Z"
    - latency: 8.60625ms
      message: 'load-balancer-api-internal: resolved host name a266be3e8ca464c8c94763466adb989a-b722817bd6027bdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T02:47:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T02:45:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-170-to-network-check-target-ip-10-0-131-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-170.ec2.internal
      uid: cdd183e8-8de5-46c5-b2ca-fd27fd9265f3
    resourceVersion: "24151"
    uid: 1c7edac3-6ae9-414f-8e4d-22923e459f18
  spec:
    sourcePod: network-check-source-8894fc9bd-crw5h
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T02:52:53Z"
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.48254ms
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:52:53Z"
    - latency: 827.437µs
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:51:53Z"
    - latency: 842.581µs
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:50:53Z"
    - latency: 879.735µs
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:49:53Z"
    - latency: 889.921µs
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:48:53Z"
    - latency: 1.132947ms
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:47:53Z"
    - latency: 1.214412ms
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:46:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T02:45:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-170-to-network-check-target-ip-10-0-134-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-170.ec2.internal
      uid: cdd183e8-8de5-46c5-b2ca-fd27fd9265f3
    resourceVersion: "24153"
    uid: d8c2a84c-92c4-4789-a1f0-2cb902f6df36
  spec:
    sourcePod: network-check-source-8894fc9bd-crw5h
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T02:52:53Z"
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.999019ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:52:53Z"
    - latency: 2.207985ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:51:53Z"
    - latency: 2.213365ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:50:53Z"
    - latency: 1.895003ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:49:53Z"
    - latency: 2.093706ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:48:53Z"
    - latency: 2.251336ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:47:53Z"
    - latency: 2.627315ms
      message: 'network-check-target-ip-10-0-134-66: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:46:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T02:45:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-170-to-network-check-target-ip-10-0-137-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-170.ec2.internal
      uid: cdd183e8-8de5-46c5-b2ca-fd27fd9265f3
    resourceVersion: "24152"
    uid: 15a121bb-98cb-40df-8f8f-c1447237f13c
  spec:
    sourcePod: network-check-source-8894fc9bd-crw5h
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T02:52:53Z"
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.67942ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:52:53Z"
    - latency: 2.055007ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:51:53Z"
    - latency: 2.345134ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:50:53Z"
    - latency: 2.204051ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:49:53Z"
    - latency: 2.073506ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:48:53Z"
    - latency: 2.330124ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:47:53Z"
    - latency: 2.454728ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:46:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T02:45:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-170-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-170.ec2.internal
      uid: cdd183e8-8de5-46c5-b2ca-fd27fd9265f3
    resourceVersion: "23012"
    uid: b9eb39e9-79bf-430d-859f-1ad1b87cbebd
  spec:
    sourcePod: network-check-source-8894fc9bd-crw5h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T02:51:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.062798ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:51:53Z"
    - latency: 1.881481ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T02:51:53Z"
    - latency: 1.16247ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:50:53Z"
    - latency: 1.759825ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T02:50:53Z"
    - latency: 910.928µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:49:53Z"
    - latency: 1.717269ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T02:49:53Z"
    - latency: 898.311µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:48:53Z"
    - latency: 1.841202ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T02:48:53Z"
    - latency: 859.143µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T02:47:53Z"
    - latency: 1.8326ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T02:47:53Z"
kind: List
metadata:
  resourceVersion: ""