apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:27:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-250-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-250.ec2.internal uid: f43c40d3-cd5b-438b-a9f4-fc031b50d837 resourceVersion: "30237" uid: f0a5ff91-5ae9-4022-9d59-7b6e85ff21de spec: sourcePod: network-check-source-6947749cfc-p5df5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-12T22:34:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.876882ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:41:53Z" - latency: 1.373ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:40:53Z" - latency: 822.722µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:39:53Z" - latency: 1.192477ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:38:53Z" - latency: 1.176078ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:37:53Z" - latency: 1.259718ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:36:53Z" - latency: 912.964µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:35:53Z" - latency: 903.512µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:34:53Z" - latency: 832.73µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:33:53Z" - latency: 1.279149ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:32:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:27:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-250-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-250.ec2.internal uid: f43c40d3-cd5b-438b-a9f4-fc031b50d837 resourceVersion: "28966" uid: 8864f63b-22a3-463b-8167-efd13db58fcc spec: sourcePod: network-check-source-6947749cfc-p5df5 targetEndpoint: ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T22:33:53Z" message: 'load-balancer-api-external: tcp connection to ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.919234ms message: 'load-balancer-api-external: tcp connection to ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:39:53Z" - latency: 7.016793ms message: 'load-balancer-api-external: resolved host name ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:39:53Z" - latency: 5.405609ms message: 'load-balancer-api-external: tcp connection to ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:38:53Z" - latency: 6.519801ms message: 'load-balancer-api-external: resolved host name ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:38:53Z" - latency: 6.150179ms message: 'load-balancer-api-external: tcp connection to ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:37:53Z" - latency: 8.459893ms message: 'load-balancer-api-external: resolved host name ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:37:53Z" - latency: 4.848353ms message: 'load-balancer-api-external: tcp connection to ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:36:53Z" - latency: 8.766136ms message: 'load-balancer-api-external: resolved host name ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:36:53Z" - latency: 3.792375ms message: 'load-balancer-api-external: tcp connection to ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:35:53Z" - latency: 7.979625ms message: 'load-balancer-api-external: resolved host name ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:35:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:27:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-250-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-250.ec2.internal uid: f43c40d3-cd5b-438b-a9f4-fc031b50d837 resourceVersion: "28967" uid: 053553a7-2d63-40b6-a740-f3ce797a5270 spec: sourcePod: network-check-source-6947749cfc-p5df5 targetEndpoint: ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T22:33:53Z" message: 'load-balancer-api-internal: tcp connection to ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.90365ms message: 'load-balancer-api-internal: tcp connection to ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:39:53Z" - latency: 6.889256ms message: 'load-balancer-api-internal: resolved host name ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:39:53Z" - latency: 5.436198ms message: 'load-balancer-api-internal: tcp connection to ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:38:53Z" - latency: 6.571774ms message: 'load-balancer-api-internal: resolved host name ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:38:53Z" - latency: 6.184771ms message: 'load-balancer-api-internal: tcp connection to ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:37:53Z" - latency: 8.41829ms message: 'load-balancer-api-internal: resolved host name ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:37:53Z" - latency: 4.873748ms message: 'load-balancer-api-internal: tcp connection to ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:36:53Z" - latency: 8.637547ms message: 'load-balancer-api-internal: resolved host name ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:36:53Z" - latency: 5.19811ms message: 'load-balancer-api-internal: tcp connection to ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:35:53Z" - latency: 7.880336ms message: 'load-balancer-api-internal: resolved host name ae6585b35a3924640b842af11bd9d883-21c9e0d0af0a002a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T22:35:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:27:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-250-to-network-check-target-ip-10-0-131-3 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-250.ec2.internal uid: f43c40d3-cd5b-438b-a9f4-fc031b50d837 resourceVersion: "30235" uid: 19c3b81b-81d9-46c2-9152-6ba3c816ff1e spec: sourcePod: network-check-source-6947749cfc-p5df5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-12T22:34:53Z" message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.336943ms message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:41:53Z" - latency: 1.955936ms message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:40:53Z" - latency: 2.050888ms message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:39:53Z" - latency: 1.911823ms message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:38:53Z" - latency: 1.989812ms message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:37:53Z" - latency: 2.073713ms message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:36:53Z" - latency: 2.171558ms message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:35:53Z" - latency: 2.237934ms message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:34:53Z" - latency: 2.517986ms message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:33:53Z" - latency: 2.585628ms message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:32:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:27:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-250-to-network-check-target-ip-10-0-133-122 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-250.ec2.internal uid: f43c40d3-cd5b-438b-a9f4-fc031b50d837 resourceVersion: "30236" uid: 6c1d5465-4955-4003-834a-6774824f0f9d spec: sourcePod: network-check-source-6947749cfc-p5df5 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T22:34:53Z" message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.300247ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:41:53Z" - latency: 1.927973ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:40:53Z" - latency: 1.82958ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:39:53Z" - latency: 1.944524ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:38:53Z" - latency: 1.955581ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:37:53Z" - latency: 2.160727ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:36:53Z" - latency: 2.233736ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:35:53Z" - latency: 2.266331ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:34:53Z" - latency: 1.697136ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:33:53Z" - latency: 2.149631ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:32:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:27:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-250-to-network-check-target-ip-10-0-135-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-250.ec2.internal uid: f43c40d3-cd5b-438b-a9f4-fc031b50d837 resourceVersion: "30234" uid: a14ec93c-81bd-4ae8-a12d-5486834ae9c7 spec: sourcePod: network-check-source-6947749cfc-p5df5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T22:34:53Z" message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.010339ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:41:53Z" - latency: 1.337988ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:40:53Z" - latency: 716.243µs message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:39:53Z" - latency: 900.487µs message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:38:53Z" - latency: 947.302µs message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:37:53Z" - latency: 1.002661ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:36:53Z" - latency: 836.45µs message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:35:53Z" - latency: 1.494515ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:34:53Z" - latency: 1.695937ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:33:53Z" - latency: 1.310541ms message: 'network-check-target-ip-10-0-135-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:32:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T22:27:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-250-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-250.ec2.internal uid: f43c40d3-cd5b-438b-a9f4-fc031b50d837 resourceVersion: "28965" uid: e0c5211b-28ac-4f1b-bf11-1b721ee4b61b spec: sourcePod: network-check-source-6947749cfc-p5df5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-12T22:33:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.132021ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:39:53Z" - latency: 1.602925ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:39:53Z" - latency: 679.473µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:38:53Z" - latency: 1.83783ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:38:53Z" - latency: 866.288µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:37:53Z" - latency: 2.315243ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:37:53Z" - latency: 864.927µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:36:53Z" - latency: 2.144319ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:36:53Z" - latency: 883.983µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T22:35:53Z" - latency: 1.559696ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T22:35:53Z" kind: List metadata: resourceVersion: ""