apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T21:24:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-213-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-213.ec2.internal uid: 88472cfb-cd78-4494-be71-1f6c5654d35c resourceVersion: "54391" uid: a37ffb9b-9487-418d-9835-11efb687813d spec: sourcePod: network-check-source-869dcfcdcd-ljr87 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T21:31:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 947.705µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:59:13Z" - latency: 1.47438ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:58:13Z" - latency: 1.184754ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:57:13Z" - latency: 972.457µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:56:13Z" - latency: 1.560208ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:55:13Z" - latency: 1.488734ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:54:13Z" - latency: 967.059µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:53:13Z" - latency: 881.528µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:52:13Z" - latency: 938.54µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:51:13Z" - latency: 1.396769ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:50:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T21:24:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-213-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-213.ec2.internal uid: 88472cfb-cd78-4494-be71-1f6c5654d35c resourceVersion: "55376" uid: 9becf143-571d-40f9-a8b6-0408e8473eb1 spec: sourcePod: network-check-source-869dcfcdcd-ljr87 targetEndpoint: ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T21:30:13Z" message: 'load-balancer-api-external: tcp connection to ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.38014ms message: 'load-balancer-api-external: tcp connection to ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:00:13Z" - latency: 6.116889ms message: 'load-balancer-api-external: resolved host name ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T22:00:13Z" - latency: 4.745012ms message: 'load-balancer-api-external: tcp connection to ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:59:13Z" - latency: 7.164709ms message: 'load-balancer-api-external: resolved host name ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:59:13Z" - latency: 4.482902ms message: 'load-balancer-api-external: tcp connection to ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:58:13Z" - latency: 6.073293ms message: 'load-balancer-api-external: resolved host name ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:58:13Z" - latency: 3.768567ms message: 'load-balancer-api-external: tcp connection to ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:57:13Z" - latency: 7.351256ms message: 'load-balancer-api-external: resolved host name ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:57:13Z" - latency: 4.551347ms message: 'load-balancer-api-external: tcp connection to ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:56:13Z" - latency: 6.678966ms message: 'load-balancer-api-external: resolved host name ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:56:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T21:24:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-213-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-213.ec2.internal uid: 88472cfb-cd78-4494-be71-1f6c5654d35c resourceVersion: "55375" uid: 4e368a5d-3991-4cc0-9588-c1c1cc7033f3 spec: sourcePod: network-check-source-869dcfcdcd-ljr87 targetEndpoint: ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T21:30:13Z" message: 'load-balancer-api-internal: tcp connection to ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.356812ms message: 'load-balancer-api-internal: tcp connection to ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:00:13Z" - latency: 6.085244ms message: 'load-balancer-api-internal: resolved host name ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T22:00:13Z" - latency: 4.277597ms message: 'load-balancer-api-internal: tcp connection to ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:59:13Z" - latency: 7.132318ms message: 'load-balancer-api-internal: resolved host name ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:59:13Z" - latency: 4.49571ms message: 'load-balancer-api-internal: tcp connection to ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:58:13Z" - latency: 6.03556ms message: 'load-balancer-api-internal: resolved host name ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:58:13Z" - latency: 3.800825ms message: 'load-balancer-api-internal: tcp connection to ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:57:13Z" - latency: 7.297471ms message: 'load-balancer-api-internal: resolved host name ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:57:13Z" - latency: 4.53148ms message: 'load-balancer-api-internal: tcp connection to ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:56:13Z" - latency: 6.656582ms message: 'load-balancer-api-internal: resolved host name ac1fd64581cb54dc7bafeb3b6da0abab-f8a75e96da1bea44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:56:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T21:24:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-213-to-network-check-target-ip-10-0-130-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-213.ec2.internal uid: 88472cfb-cd78-4494-be71-1f6c5654d35c resourceVersion: "54388" uid: 2c292d38-fbb3-412c-a81b-3e9c5a79bdad spec: sourcePod: network-check-source-869dcfcdcd-ljr87 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T21:31:13Z" message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.072398ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:59:13Z" - latency: 955.802µs message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:58:13Z" - latency: 1.470993ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:57:13Z" - latency: 823.383µs message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:56:13Z" - latency: 812.341µs message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:55:13Z" - latency: 1.227328ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:54:13Z" - latency: 898.753µs message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:53:13Z" - latency: 817.997µs message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:52:13Z" - latency: 814.997µs message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:51:13Z" - latency: 1.051129ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:50:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T21:24:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-213-to-network-check-target-ip-10-0-133-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-213.ec2.internal uid: 88472cfb-cd78-4494-be71-1f6c5654d35c resourceVersion: "54389" uid: cf9f8271-988c-4529-8885-33448179e096 spec: sourcePod: network-check-source-869dcfcdcd-ljr87 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T21:31:13Z" message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.334318ms message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:59:13Z" - latency: 2.555651ms message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:58:13Z" - latency: 2.176831ms message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:57:13Z" - latency: 2.4086ms message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:56:13Z" - latency: 1.965988ms message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:55:13Z" - latency: 2.428455ms message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:54:13Z" - latency: 3.269562ms message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:53:13Z" - latency: 2.02858ms message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:52:13Z" - latency: 2.042529ms message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:51:13Z" - latency: 2.699423ms message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:50:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T21:24:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-213-to-network-check-target-ip-10-0-141-131 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-213.ec2.internal uid: 88472cfb-cd78-4494-be71-1f6c5654d35c resourceVersion: "54390" uid: 4cbc85cc-a030-4d3f-9bac-adcd87ee3cd7 spec: sourcePod: network-check-source-869dcfcdcd-ljr87 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T21:31:13Z" message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.615136ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:59:13Z" - latency: 2.266726ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:58:13Z" - latency: 2.769077ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:57:13Z" - latency: 2.344158ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:56:13Z" - latency: 2.440908ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:55:13Z" - latency: 2.200396ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:54:13Z" - latency: 2.354827ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:53:13Z" - latency: 2.400463ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:52:13Z" - latency: 2.014899ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:51:13Z" - latency: 2.434481ms message: 'network-check-target-ip-10-0-141-131: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:50:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T21:24:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-213-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-213.ec2.internal uid: 88472cfb-cd78-4494-be71-1f6c5654d35c resourceVersion: "55374" uid: 4ea9a6c7-8784-4131-86a5-ad80de4ac917 spec: sourcePod: network-check-source-869dcfcdcd-ljr87 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T21:30:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 852.329µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T22:00:13Z" - latency: 1.792856ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T22:00:13Z" - latency: 810.102µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:59:13Z" - latency: 1.983522ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:59:13Z" - latency: 937.189µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:58:13Z" - latency: 1.716223ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:58:13Z" - latency: 802.528µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:57:13Z" - latency: 1.850225ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:57:13Z" - latency: 1.20979ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:56:13Z" - latency: 1.792717ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:56:13Z" kind: List metadata: resourceVersion: ""