apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-23T03:28:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-18-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-18.ec2.internal uid: ea1f54da-12c0-4925-b7fb-5b1b78d30745 resourceVersion: "23243" uid: d83963e0-dc80-48ec-a70a-97faa8e91612 spec: sourcePod: network-check-source-757774bcb8-qhn45 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-23T03:35:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 996.725µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:10:51Z" - latency: 851.034µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:09:51Z" - latency: 1.300624ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:08:51Z" - latency: 712.614µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:07:51Z" - latency: 881.66µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:06:51Z" - latency: 863.541µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:05:51Z" - latency: 879.411µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:04:51Z" - latency: 860.801µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:03:51Z" - latency: 897.409µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:02:51Z" - latency: 846.855µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:01:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-23T03:28:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-18-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-18.ec2.internal uid: ea1f54da-12c0-4925-b7fb-5b1b78d30745 resourceVersion: "23244" uid: 10ce3485-5ea8-43a5-b2b1-3108bb757602 spec: sourcePod: network-check-source-757774bcb8-qhn45 targetEndpoint: acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-23T03:34:51Z" message: 'load-balancer-api-external: tcp connection to acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 14.806607ms message: 'load-balancer-api-external: tcp connection to acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:10:51Z" - latency: 8.760383ms message: 'load-balancer-api-external: resolved host name acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-23T04:10:51Z" - latency: 15.605316ms message: 'load-balancer-api-external: tcp connection to acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:09:51Z" - latency: 7.828746ms message: 'load-balancer-api-external: resolved host name acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-23T04:09:51Z" - latency: 32.834671ms message: 'load-balancer-api-external: tcp connection to acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:08:51Z" - latency: 6.862315ms message: 'load-balancer-api-external: resolved host name acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-23T04:08:51Z" - latency: 17.031189ms message: 'load-balancer-api-external: tcp connection to acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:07:51Z" - latency: 7.961009ms message: 'load-balancer-api-external: resolved host name acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-23T04:07:51Z" - latency: 16.647273ms message: 'load-balancer-api-external: tcp connection to acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:06:51Z" - latency: 7.29052ms message: 'load-balancer-api-external: resolved host name acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-23T04:06:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-23T03:28:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-18-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-18.ec2.internal uid: ea1f54da-12c0-4925-b7fb-5b1b78d30745 resourceVersion: "23245" uid: 426da2e8-a0b2-4282-a848-aafeb5dca16b spec: sourcePod: network-check-source-757774bcb8-qhn45 targetEndpoint: acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-23T03:34:51Z" message: 'load-balancer-api-internal: tcp connection to acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.500452ms message: 'load-balancer-api-internal: tcp connection to acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:10:51Z" - latency: 8.82715ms message: 'load-balancer-api-internal: resolved host name acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-23T04:10:51Z" - latency: 16.954989ms message: 'load-balancer-api-internal: tcp connection to acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:09:51Z" - latency: 7.914713ms message: 'load-balancer-api-internal: resolved host name acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-23T04:09:51Z" - latency: 16.712539ms message: 'load-balancer-api-internal: tcp connection to acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:08:51Z" - latency: 6.905856ms message: 'load-balancer-api-internal: resolved host name acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-23T04:08:51Z" - latency: 31.215817ms message: 'load-balancer-api-internal: tcp connection to acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:07:51Z" - latency: 7.93447ms message: 'load-balancer-api-internal: resolved host name acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-23T04:07:51Z" - latency: 16.679439ms message: 'load-balancer-api-internal: tcp connection to acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:06:51Z" - latency: 7.264134ms message: 'load-balancer-api-internal: resolved host name acf7deaca82fc4ea38e1adcb47fbb0ff-544aceec4a2b4edf.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-23T04:06:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-23T03:28:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-18-to-network-check-target-ip-10-0-138-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-18.ec2.internal uid: ea1f54da-12c0-4925-b7fb-5b1b78d30745 resourceVersion: "23241" uid: cb91f891-7ea3-4ea5-b55f-82f668c78547 spec: sourcePod: network-check-source-757774bcb8-qhn45 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-23T03:35:51Z" message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.358155ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:10:51Z" - latency: 2.119063ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:09:51Z" - latency: 2.156625ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:08:51Z" - latency: 2.080373ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:07:51Z" - latency: 1.922636ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:06:51Z" - latency: 2.013609ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:05:51Z" - latency: 1.942474ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:04:51Z" - latency: 2.018302ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:03:51Z" - latency: 2.281947ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:02:51Z" - latency: 2.198949ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:01:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-23T03:28:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-18-to-network-check-target-ip-10-0-140-191 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-18.ec2.internal uid: ea1f54da-12c0-4925-b7fb-5b1b78d30745 resourceVersion: "23239" uid: e20d9ef2-6519-4736-8830-0480600f367e spec: sourcePod: network-check-source-757774bcb8-qhn45 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-23T03:35:51Z" message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.901856ms message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:10:51Z" - latency: 1.821454ms message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:09:51Z" - latency: 2.362183ms message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:08:51Z" - latency: 1.889319ms message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:07:51Z" - latency: 1.849361ms message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:06:51Z" - latency: 1.875962ms message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:05:51Z" - latency: 2.000851ms message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:04:51Z" - latency: 1.677404ms message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:03:51Z" - latency: 1.846292ms message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:02:51Z" - latency: 2.257815ms message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:01:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-23T03:28:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-18-to-network-check-target-ip-10-0-143-18 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-18.ec2.internal uid: ea1f54da-12c0-4925-b7fb-5b1b78d30745 resourceVersion: "23240" uid: 342633fa-1777-4026-9e14-a6e53fef445b spec: sourcePod: network-check-source-757774bcb8-qhn45 targetEndpoint: 10.132.0.6:8080 status: conditions: - lastTransitionTime: "2026-10-23T03:35:51Z" message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.132.0.6:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 713.095µs message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.132.0.6:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:10:51Z" - latency: 811.763µs message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.132.0.6:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:09:51Z" - latency: 806.681µs message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.132.0.6:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:08:51Z" - latency: 734.134µs message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.132.0.6:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:07:51Z" - latency: 815.364µs message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.132.0.6:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:06:51Z" - latency: 837.637µs message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.132.0.6:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:05:51Z" - latency: 749.625µs message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.132.0.6:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:04:51Z" - latency: 750.611µs message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.132.0.6:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:03:51Z" - latency: 1.292766ms message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.132.0.6:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:02:51Z" - latency: 719.66µs message: 'network-check-target-ip-10-0-143-18: tcp connection to 10.132.0.6:8080 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:01:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-23T03:28:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-18-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-18.ec2.internal uid: ea1f54da-12c0-4925-b7fb-5b1b78d30745 resourceVersion: "23242" uid: 72bfff6b-38ab-4a69-a167-04e0e55895d4 spec: sourcePod: network-check-source-757774bcb8-qhn45 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-23T03:34:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 941.737µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:10:51Z" - latency: 1.800187ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-23T04:10:51Z" - latency: 1.261672ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:09:51Z" - latency: 1.578803ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-23T04:09:51Z" - latency: 1.426972ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:08:51Z" - latency: 1.796566ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-23T04:08:51Z" - latency: 867.266µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:07:51Z" - latency: 2.249586ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-23T04:07:51Z" - latency: 878.77µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-23T04:06:51Z" - latency: 1.809284ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-23T04:06:51Z" kind: List metadata: resourceVersion: ""