apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:56:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-12-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-12.ec2.internal
      uid: 79c98602-8c06-4b6d-b792-2d74a2762886
    resourceVersion: "23587"
    uid: b7babf4b-1599-4455-a2c5-11955f9e2f1e
  spec:
    sourcePod: network-check-source-8894fc9bd-4lcdx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:03:21Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 915.689µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:03:21Z"
    - latency: 985.552µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:02:21Z"
    - latency: 1.000517ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:01:21Z"
    - latency: 1.842929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:00:21Z"
    - latency: 923.242µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:59:21Z"
    - latency: 920.015µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:58:21Z"
    - latency: 1.141239ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:57:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:56:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-12-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-12.ec2.internal
      uid: 79c98602-8c06-4b6d-b792-2d74a2762886
    resourceVersion: "22383"
    uid: 8957129d-671f-4643-9f42-ef26eae839ae
  spec:
    sourcePod: network-check-source-8894fc9bd-4lcdx
    targetEndpoint: a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:02:21Z"
      message: 'load-balancer-api-external: tcp connection to a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.622639ms
      message: 'load-balancer-api-external: tcp connection to a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:02:21Z"
    - latency: 6.876129ms
      message: 'load-balancer-api-external: resolved host name a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:02:21Z"
    - latency: 4.37775ms
      message: 'load-balancer-api-external: tcp connection to a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:01:21Z"
    - latency: 13.211715ms
      message: 'load-balancer-api-external: resolved host name a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:01:21Z"
    - latency: 5.714509ms
      message: 'load-balancer-api-external: tcp connection to a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:00:21Z"
    - latency: 7.677141ms
      message: 'load-balancer-api-external: resolved host name a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:00:21Z"
    - latency: 4.258142ms
      message: 'load-balancer-api-external: tcp connection to a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:59:21Z"
    - latency: 8.259636ms
      message: 'load-balancer-api-external: resolved host name a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:59:21Z"
    - latency: 5.572837ms
      message: 'load-balancer-api-external: tcp connection to a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:58:21Z"
    - latency: 8.096549ms
      message: 'load-balancer-api-external: resolved host name a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:58:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:56:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-12-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-12.ec2.internal
      uid: 79c98602-8c06-4b6d-b792-2d74a2762886
    resourceVersion: "22384"
    uid: cd603a51-5d2a-4d0e-a534-b36711434438
  spec:
    sourcePod: network-check-source-8894fc9bd-4lcdx
    targetEndpoint: a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:02:21Z"
      message: 'load-balancer-api-internal: tcp connection to a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.118118ms
      message: 'load-balancer-api-internal: tcp connection to a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:02:21Z"
    - latency: 6.726191ms
      message: 'load-balancer-api-internal: resolved host name a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:02:21Z"
    - latency: 4.165227ms
      message: 'load-balancer-api-internal: tcp connection to a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:01:21Z"
    - latency: 13.169558ms
      message: 'load-balancer-api-internal: resolved host name a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:01:21Z"
    - latency: 5.728165ms
      message: 'load-balancer-api-internal: tcp connection to a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:00:21Z"
    - latency: 7.617817ms
      message: 'load-balancer-api-internal: resolved host name a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:00:21Z"
    - latency: 4.429612ms
      message: 'load-balancer-api-internal: tcp connection to a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:59:21Z"
    - latency: 8.217864ms
      message: 'load-balancer-api-internal: resolved host name a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:59:21Z"
    - latency: 5.617192ms
      message: 'load-balancer-api-internal: tcp connection to a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:58:21Z"
    - latency: 8.070572ms
      message: 'load-balancer-api-internal: resolved host name a2bc1cd80d9f24c26a51030ca205e767-8d026707ffd5858e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:58:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:56:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-12-to-network-check-target-ip-10-0-128-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-12.ec2.internal
      uid: 79c98602-8c06-4b6d-b792-2d74a2762886
    resourceVersion: "23583"
    uid: 2b0478c5-25b2-4cb3-8518-f3b68dc67e5a
  spec:
    sourcePod: network-check-source-8894fc9bd-4lcdx
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:03:21Z"
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.318348ms
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:03:21Z"
    - latency: 1.942742ms
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:02:21Z"
    - latency: 2.383512ms
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:01:21Z"
    - latency: 2.727405ms
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:00:21Z"
    - latency: 2.520132ms
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:59:21Z"
    - latency: 2.551064ms
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:58:21Z"
    - latency: 2.803086ms
      message: 'network-check-target-ip-10-0-128-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:57:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:56:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-12-to-network-check-target-ip-10-0-130-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-12.ec2.internal
      uid: 79c98602-8c06-4b6d-b792-2d74a2762886
    resourceVersion: "23584"
    uid: a80e55d8-ad8b-41b1-a972-764ad2473cd3
  spec:
    sourcePod: network-check-source-8894fc9bd-4lcdx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:03:21Z"
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.307666ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:03:21Z"
    - latency: 2.198101ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:02:21Z"
    - latency: 2.431541ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:01:21Z"
    - latency: 2.444984ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:00:21Z"
    - latency: 2.310764ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:59:21Z"
    - latency: 2.123241ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:58:21Z"
    - latency: 2.273151ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:57:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:56:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-12-to-network-check-target-ip-10-0-132-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-12.ec2.internal
      uid: 79c98602-8c06-4b6d-b792-2d74a2762886
    resourceVersion: "23580"
    uid: 7b7e0649-61d7-4def-ada5-5bf56eaa5461
  spec:
    sourcePod: network-check-source-8894fc9bd-4lcdx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:03:21Z"
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 815.308µs
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:03:21Z"
    - latency: 930.149µs
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:02:21Z"
    - latency: 765.184µs
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:01:21Z"
    - latency: 1.041614ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:00:21Z"
    - latency: 768.723µs
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:59:21Z"
    - latency: 924.434µs
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:58:21Z"
    - latency: 1.140986ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:57:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:56:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-12-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-12.ec2.internal
      uid: 79c98602-8c06-4b6d-b792-2d74a2762886
    resourceVersion: "22382"
    uid: 7f9a8147-6097-4157-8f43-dc0d60a68526
  spec:
    sourcePod: network-check-source-8894fc9bd-4lcdx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:02:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.012617ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:02:21Z"
    - latency: 1.834225ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:02:21Z"
    - latency: 7.97643ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:01:21Z"
    - latency: 2.137991ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:01:21Z"
    - latency: 1.187236ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:00:21Z"
    - latency: 1.88004ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:00:21Z"
    - latency: 841.794µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:59:21Z"
    - latency: 1.552819ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:59:21Z"
    - latency: 993.761µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:58:21Z"
    - latency: 1.652425ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:58:21Z"
kind: List
metadata:
  resourceVersion: ""