apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:06:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-76-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-76.ec2.internal uid: 14c95c06-4381-457a-8976-a3669faca78b resourceVersion: "21858" uid: 80be3556-ec15-401c-82f3-1cf2dbc381be spec: sourcePod: network-check-source-869dcfcdcd-h8zvk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T18:13:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 894.646µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:27:57Z" - latency: 914.9µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:26:57Z" - latency: 926.147µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:57Z" - latency: 1.286111ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:57Z" - latency: 1.095894ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:57Z" - latency: 1.198625ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:57Z" - latency: 1.169826ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:57Z" - latency: 1.245981ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:20:57Z" - latency: 1.143587ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:19:57Z" - latency: 948.42µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:18:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:06:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-76-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-76.ec2.internal uid: 14c95c06-4381-457a-8976-a3669faca78b resourceVersion: "20410" uid: 73579ba4-94c4-47cb-90fa-2935ff618372 spec: sourcePod: network-check-source-869dcfcdcd-h8zvk targetEndpoint: ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T18:12:57Z" message: 'load-balancer-api-external: tcp connection to ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.75745ms message: 'load-balancer-api-external: tcp connection to ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:57Z" - latency: 6.681067ms message: 'load-balancer-api-external: resolved host name ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:24:57Z" - latency: 5.683688ms message: 'load-balancer-api-external: tcp connection to ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:57Z" - latency: 6.967617ms message: 'load-balancer-api-external: resolved host name ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:23:57Z" - latency: 5.01731ms message: 'load-balancer-api-external: tcp connection to ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:57Z" - latency: 6.668965ms message: 'load-balancer-api-external: resolved host name ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:22:57Z" - latency: 6.140901ms message: 'load-balancer-api-external: tcp connection to ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:57Z" - latency: 6.713668ms message: 'load-balancer-api-external: resolved host name ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:21:57Z" - latency: 5.467135ms message: 'load-balancer-api-external: tcp connection to ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:20:57Z" - latency: 6.748949ms message: 'load-balancer-api-external: resolved host name ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:20:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:06:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-76-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-76.ec2.internal uid: 14c95c06-4381-457a-8976-a3669faca78b resourceVersion: "20411" uid: 57cf909d-b8e3-4202-baba-047c01c05f3e spec: sourcePod: network-check-source-869dcfcdcd-h8zvk targetEndpoint: ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T18:12:57Z" message: 'load-balancer-api-internal: tcp connection to ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.239799ms message: 'load-balancer-api-internal: tcp connection to ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:57Z" - latency: 6.614747ms message: 'load-balancer-api-internal: resolved host name ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:24:57Z" - latency: 5.670074ms message: 'load-balancer-api-internal: tcp connection to ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:57Z" - latency: 6.89848ms message: 'load-balancer-api-internal: resolved host name ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:23:57Z" - latency: 4.450561ms message: 'load-balancer-api-internal: tcp connection to ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:57Z" - latency: 6.773255ms message: 'load-balancer-api-internal: resolved host name ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:22:57Z" - latency: 5.401685ms message: 'load-balancer-api-internal: tcp connection to ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:57Z" - latency: 6.580143ms message: 'load-balancer-api-internal: resolved host name ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:21:57Z" - latency: 5.149305ms message: 'load-balancer-api-internal: tcp connection to ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:20:57Z" - latency: 6.577136ms message: 'load-balancer-api-internal: resolved host name ad45b2c8f5eb741b89da533a8fbbe01b-c8a5d4f1eda26640.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:20:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:06:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-76-to-network-check-target-ip-10-0-133-76 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-76.ec2.internal uid: 14c95c06-4381-457a-8976-a3669faca78b resourceVersion: "21855" uid: 1a4bad41-0eb0-4313-8938-416a99e06040 spec: sourcePod: network-check-source-869dcfcdcd-h8zvk targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:13:57Z" message: 'network-check-target-ip-10-0-133-76: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.126344ms message: 'network-check-target-ip-10-0-133-76: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:27:57Z" - latency: 937.925µs message: 'network-check-target-ip-10-0-133-76: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:26:57Z" - latency: 1.078139ms message: 'network-check-target-ip-10-0-133-76: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:57Z" - latency: 958.922µs message: 'network-check-target-ip-10-0-133-76: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:57Z" - latency: 1.043724ms message: 'network-check-target-ip-10-0-133-76: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:57Z" - latency: 1.454199ms message: 'network-check-target-ip-10-0-133-76: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:57Z" - latency: 1.070179ms message: 'network-check-target-ip-10-0-133-76: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:57Z" - latency: 1.103077ms message: 'network-check-target-ip-10-0-133-76: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:20:57Z" - latency: 906.182µs message: 'network-check-target-ip-10-0-133-76: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:19:57Z" - latency: 1.144037ms message: 'network-check-target-ip-10-0-133-76: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:18:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:06:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-76-to-network-check-target-ip-10-0-137-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-76.ec2.internal uid: 14c95c06-4381-457a-8976-a3669faca78b resourceVersion: "21856" uid: 01d913df-e8c2-4209-9407-c0fd4a7ea545 spec: sourcePod: network-check-source-869dcfcdcd-h8zvk targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:13:57Z" message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.167478ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:27:57Z" - latency: 2.010546ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:26:57Z" - latency: 2.338128ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:57Z" - latency: 2.247456ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:57Z" - latency: 2.29371ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:57Z" - latency: 2.351782ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:57Z" - latency: 2.359755ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:57Z" - latency: 2.240618ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:20:57Z" - latency: 2.355879ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:19:57Z" - latency: 2.061152ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:18:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:06:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-76-to-network-check-target-ip-10-0-143-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-76.ec2.internal uid: 14c95c06-4381-457a-8976-a3669faca78b resourceVersion: "21857" uid: a13de0f9-0002-499e-9eca-1d0c4f944e63 spec: sourcePod: network-check-source-869dcfcdcd-h8zvk targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:13:57Z" message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.1368ms message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:27:57Z" - latency: 2.02703ms message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:26:57Z" - latency: 2.579823ms message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:57Z" - latency: 2.258068ms message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:57Z" - latency: 2.331481ms message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:57Z" - latency: 2.184316ms message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:57Z" - latency: 2.209711ms message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:57Z" - latency: 2.345492ms message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:20:57Z" - latency: 2.263114ms message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:19:57Z" - latency: 1.997172ms message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:18:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:06:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-76-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-76.ec2.internal uid: 14c95c06-4381-457a-8976-a3669faca78b resourceVersion: "20409" uid: 4c52fa01-aac4-431f-894e-eb12801ebd78 spec: sourcePod: network-check-source-869dcfcdcd-h8zvk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T18:12:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 930.962µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:57Z" - latency: 1.782753ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:24:57Z" - latency: 989.223µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:57Z" - latency: 1.853821ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:23:57Z" - latency: 1.209244ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:57Z" - latency: 1.960479ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:22:57Z" - latency: 940.242µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:57Z" - latency: 1.780218ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:21:57Z" - latency: 873.963µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:20:57Z" - latency: 1.745599ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:20:57Z" kind: List metadata: resourceVersion: ""