apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:06:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-73-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-73.ec2.internal uid: 3ca3ddca-3348-4570-af00-945921d82447 resourceVersion: "31588" uid: 8797cf96-3be9-4b21-b51a-43d72f76d04b spec: sourcePod: network-check-source-8894fc9bd-w964t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-21T10:13:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.036246ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:48:29Z" - latency: 1.059269ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:47:29Z" - latency: 899.567µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:46:29Z" - latency: 762.488µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:45:29Z" - latency: 901.517µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:44:29Z" - latency: 1.078408ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:43:29Z" - latency: 911.808µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:42:29Z" - latency: 911.347µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:41:29Z" - latency: 944.349µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:40:29Z" - latency: 1.3211ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:39:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:06:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-73-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-73.ec2.internal uid: 3ca3ddca-3348-4570-af00-945921d82447 resourceVersion: "31590" uid: 4d55e6a5-7109-4b9d-899b-391f897b0c42 spec: sourcePod: network-check-source-8894fc9bd-w964t targetEndpoint: a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T10:12:29Z" message: 'load-balancer-api-external: tcp connection to a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.170949ms message: 'load-balancer-api-external: tcp connection to a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:48:29Z" - latency: 8.449819ms message: 'load-balancer-api-external: resolved host name a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:48:29Z" - latency: 4.894543ms message: 'load-balancer-api-external: tcp connection to a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:47:29Z" - latency: 8.966898ms message: 'load-balancer-api-external: resolved host name a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:47:29Z" - latency: 4.982547ms message: 'load-balancer-api-external: tcp connection to a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:46:29Z" - latency: 8.855987ms message: 'load-balancer-api-external: resolved host name a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:46:29Z" - latency: 4.898199ms message: 'load-balancer-api-external: tcp connection to a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:45:29Z" - latency: 8.355184ms message: 'load-balancer-api-external: resolved host name a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:45:29Z" - latency: 5.144606ms message: 'load-balancer-api-external: tcp connection to a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:44:29Z" - latency: 8.254578ms message: 'load-balancer-api-external: resolved host name a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:44:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:06:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-73-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-73.ec2.internal uid: 3ca3ddca-3348-4570-af00-945921d82447 resourceVersion: "31589" uid: e8c4a48c-6411-4426-8723-93618f473511 spec: sourcePod: network-check-source-8894fc9bd-w964t targetEndpoint: a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T10:12:29Z" message: 'load-balancer-api-internal: tcp connection to a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.17624ms message: 'load-balancer-api-internal: tcp connection to a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:48:29Z" - latency: 8.392773ms message: 'load-balancer-api-internal: resolved host name a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:48:29Z" - latency: 4.864891ms message: 'load-balancer-api-internal: tcp connection to a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:47:29Z" - latency: 9.019205ms message: 'load-balancer-api-internal: resolved host name a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:47:29Z" - latency: 5.012993ms message: 'load-balancer-api-internal: tcp connection to a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:46:29Z" - latency: 8.735352ms message: 'load-balancer-api-internal: resolved host name a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:46:29Z" - latency: 5.835817ms message: 'load-balancer-api-internal: tcp connection to a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:45:29Z" - latency: 8.321922ms message: 'load-balancer-api-internal: resolved host name a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:45:29Z" - latency: 5.158956ms message: 'load-balancer-api-internal: tcp connection to a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:44:29Z" - latency: 8.112095ms message: 'load-balancer-api-internal: resolved host name a4c9263cd45c54b77bfd987cefd1520c-7d3c0860ad4ded1c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T10:44:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:06:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-73-to-network-check-target-ip-10-0-129-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-73.ec2.internal uid: 3ca3ddca-3348-4570-af00-945921d82447 resourceVersion: "31585" uid: 73cf5f7c-735c-4686-b587-ed6d86ea7630 spec: sourcePod: network-check-source-8894fc9bd-w964t targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-21T10:13:29Z" message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.321332ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:48:29Z" - latency: 2.178881ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:47:29Z" - latency: 2.039686ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:46:29Z" - latency: 2.232296ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:45:29Z" - latency: 2.63775ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:44:29Z" - latency: 2.111857ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:43:29Z" - latency: 2.091918ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:42:29Z" - latency: 2.095587ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:41:29Z" - latency: 2.451683ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:40:29Z" - latency: 2.303889ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:39:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:06:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-73-to-network-check-target-ip-10-0-142-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-73.ec2.internal uid: 3ca3ddca-3348-4570-af00-945921d82447 resourceVersion: "31587" uid: ce01fd30-eaa7-45bb-a768-075c8f448b03 spec: sourcePod: network-check-source-8894fc9bd-w964t targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T10:13:29Z" message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.195164ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:48:29Z" - latency: 2.660168ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:47:29Z" - latency: 2.043762ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:46:29Z" - latency: 2.152024ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:45:29Z" - latency: 2.273958ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:44:29Z" - latency: 2.489576ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:43:29Z" - latency: 2.312306ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:42:29Z" - latency: 2.112732ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:41:29Z" - latency: 2.231191ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:40:29Z" - latency: 2.11423ms message: 'network-check-target-ip-10-0-142-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:39:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:06:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-73-to-network-check-target-ip-10-0-142-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-73.ec2.internal uid: 3ca3ddca-3348-4570-af00-945921d82447 resourceVersion: "31584" uid: a8060321-abdf-4c55-ab4d-a794488faa4f spec: sourcePod: network-check-source-8894fc9bd-w964t targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-21T10:13:29Z" message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 885.039µs message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:48:29Z" - latency: 792.152µs message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:47:29Z" - latency: 787.164µs message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:46:29Z" - latency: 837.691µs message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:45:29Z" - latency: 841.869µs message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:44:29Z" - latency: 837.495µs message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:43:29Z" - latency: 806.89µs message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:42:29Z" - latency: 1.17852ms message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:41:29Z" - latency: 864.968µs message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:40:29Z" - latency: 778.928µs message: 'network-check-target-ip-10-0-142-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:39:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T10:06:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-73-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-73.ec2.internal uid: 3ca3ddca-3348-4570-af00-945921d82447 resourceVersion: "31586" uid: 95139a7e-740f-44d1-ad82-aa0f7d5de15d spec: sourcePod: network-check-source-8894fc9bd-w964t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-21T10:12:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 764.385µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:48:29Z" - latency: 1.867098ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T10:48:29Z" - latency: 697.782µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:47:29Z" - latency: 2.048942ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T10:47:29Z" - latency: 1.094712ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:46:29Z" - latency: 1.925335ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T10:46:29Z" - latency: 1.156093ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:45:29Z" - latency: 2.360639ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T10:45:29Z" - latency: 784.769µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T10:44:29Z" - latency: 1.760295ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T10:44:29Z" kind: List metadata: resourceVersion: ""