apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T18:28:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-170-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-170.ec2.internal uid: 7a270e75-da8d-43a2-86b4-ff528d0143d0 resourceVersion: "47619" uid: 078ec8f0-d8b8-4051-a63c-b2f141654146 spec: sourcePod: network-check-source-869dcfcdcd-8sjbq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-12T18:35:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.383805ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:56:23Z" - latency: 912.279µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:55:23Z" - latency: 958.739µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:54:23Z" - latency: 1.004761ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:53:23Z" - latency: 1.142397ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:52:23Z" - latency: 1.217539ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:51:23Z" - latency: 940.292µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:50:23Z" - latency: 994.774µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:49:23Z" - latency: 1.297267ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:48:23Z" - latency: 878.658µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:47:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T18:28:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-170-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-170.ec2.internal uid: 7a270e75-da8d-43a2-86b4-ff528d0143d0 resourceVersion: "50006" uid: 0f32ebf4-65b3-453f-a6ff-adfd27587e15 spec: sourcePod: network-check-source-869dcfcdcd-8sjbq targetEndpoint: a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-12T18:34:23Z" message: 'load-balancer-api-external: tcp connection to a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.375856ms message: 'load-balancer-api-external: tcp connection to a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:58:23Z" - latency: 13.499683ms message: 'load-balancer-api-external: resolved host name a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:58:23Z" - latency: 5.415339ms message: 'load-balancer-api-external: tcp connection to a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:57:23Z" - latency: 7.241641ms message: 'load-balancer-api-external: resolved host name a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:57:23Z" - latency: 4.816903ms message: 'load-balancer-api-external: tcp connection to a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:56:23Z" - latency: 7.692882ms message: 'load-balancer-api-external: resolved host name a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:56:23Z" - latency: 4.989179ms message: 'load-balancer-api-external: tcp connection to a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:55:23Z" - latency: 6.803154ms message: 'load-balancer-api-external: resolved host name a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:55:23Z" - latency: 4.891981ms message: 'load-balancer-api-external: tcp connection to a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:54:23Z" - latency: 7.589591ms message: 'load-balancer-api-external: resolved host name a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:54:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T18:28:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-170-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-170.ec2.internal uid: 7a270e75-da8d-43a2-86b4-ff528d0143d0 resourceVersion: "50005" uid: 0ce3542a-2ead-4be4-b577-e5c5192885a5 spec: sourcePod: network-check-source-869dcfcdcd-8sjbq targetEndpoint: a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-12T18:34:23Z" message: 'load-balancer-api-internal: tcp connection to a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.663685ms message: 'load-balancer-api-internal: tcp connection to a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:58:23Z" - latency: 12.760128ms message: 'load-balancer-api-internal: resolved host name a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:58:23Z" - latency: 5.406728ms message: 'load-balancer-api-internal: tcp connection to a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:57:23Z" - latency: 7.349698ms message: 'load-balancer-api-internal: resolved host name a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:57:23Z" - latency: 4.864309ms message: 'load-balancer-api-internal: tcp connection to a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:56:23Z" - latency: 7.709425ms message: 'load-balancer-api-internal: resolved host name a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:56:23Z" - latency: 4.945091ms message: 'load-balancer-api-internal: tcp connection to a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:55:23Z" - latency: 6.907208ms message: 'load-balancer-api-internal: resolved host name a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:55:23Z" - latency: 4.85744ms message: 'load-balancer-api-internal: tcp connection to a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:54:23Z" - latency: 7.631517ms message: 'load-balancer-api-internal: resolved host name a9cc0525373b24dfbbbec9793f494a74-f1a581b625564450.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T18:54:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T18:28:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-170-to-network-check-target-ip-10-0-130-164 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-170.ec2.internal uid: 7a270e75-da8d-43a2-86b4-ff528d0143d0 resourceVersion: "47617" uid: 9b780a15-7523-4706-bd6b-6889efef539c spec: sourcePod: network-check-source-869dcfcdcd-8sjbq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-12T18:35:23Z" message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.133302ms message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:56:23Z" - latency: 2.003393ms message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:55:23Z" - latency: 2.220741ms message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:54:23Z" - latency: 2.5686ms message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:53:23Z" - latency: 2.34286ms message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:52:23Z" - latency: 2.275945ms message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:51:23Z" - latency: 2.35449ms message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:50:23Z" - latency: 2.362909ms message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:49:23Z" - latency: 2.449249ms message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:48:23Z" - latency: 2.291866ms message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:47:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T18:28:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-170-to-network-check-target-ip-10-0-137-208 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-170.ec2.internal uid: 7a270e75-da8d-43a2-86b4-ff528d0143d0 resourceVersion: "47618" uid: 92b50abc-a815-4399-976b-e6367069dee7 spec: sourcePod: network-check-source-869dcfcdcd-8sjbq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-12T18:35:23Z" message: 'network-check-target-ip-10-0-137-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.667533ms message: 'network-check-target-ip-10-0-137-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:56:23Z" - latency: 2.6152ms message: 'network-check-target-ip-10-0-137-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:55:23Z" - latency: 2.936892ms message: 'network-check-target-ip-10-0-137-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:54:23Z" - latency: 3.132632ms message: 'network-check-target-ip-10-0-137-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:53:23Z" - latency: 2.739521ms message: 'network-check-target-ip-10-0-137-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:52:23Z" - latency: 2.478751ms message: 'network-check-target-ip-10-0-137-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:51:23Z" - latency: 3.095161ms message: 'network-check-target-ip-10-0-137-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:50:23Z" - latency: 2.966504ms message: 'network-check-target-ip-10-0-137-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:49:23Z" - latency: 2.87265ms message: 'network-check-target-ip-10-0-137-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:48:23Z" - latency: 2.318747ms message: 'network-check-target-ip-10-0-137-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:47:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T18:28:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-170-to-network-check-target-ip-10-0-140-170 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-170.ec2.internal uid: 7a270e75-da8d-43a2-86b4-ff528d0143d0 resourceVersion: "47616" uid: efbcde99-de01-4bad-a7c3-5af1b760f6e2 spec: sourcePod: network-check-source-869dcfcdcd-8sjbq targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-12T18:35:23Z" message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.183193ms message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:56:23Z" - latency: 1.021917ms message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:55:23Z" - latency: 1.40274ms message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:54:23Z" - latency: 1.612734ms message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:53:23Z" - latency: 905.154µs message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:52:23Z" - latency: 989.22µs message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:51:23Z" - latency: 966.833µs message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:50:23Z" - latency: 1.165477ms message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:49:23Z" - latency: 1.492349ms message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:48:23Z" - latency: 920.501µs message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:47:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T18:28:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-170-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-170.ec2.internal uid: 7a270e75-da8d-43a2-86b4-ff528d0143d0 resourceVersion: "50003" uid: 6e403326-0b4d-4d3b-bca2-7dafd4c67b32 spec: sourcePod: network-check-source-869dcfcdcd-8sjbq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-12T18:34:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.522653ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:58:23Z" - latency: 1.997687ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T18:58:23Z" - latency: 779.901µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:57:23Z" - latency: 1.973896ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T18:57:23Z" - latency: 1.082992ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:56:23Z" - latency: 1.74081ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T18:56:23Z" - latency: 925.917µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:55:23Z" - latency: 1.695278ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T18:55:23Z" - latency: 974.67µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T18:54:23Z" - latency: 2.170743ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T18:54:23Z" kind: List metadata: resourceVersion: ""