apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T20:26:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-207-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-207.ec2.internal uid: 6abe8693-aeae-43b0-b0f2-48c357271df9 resourceVersion: "46530" uid: 53379069-26f2-4242-8743-74155a28627e spec: sourcePod: network-check-source-dbd9cf844-gcvst targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-06T20:33:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.317868ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:54:25Z" - latency: 1.16899ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:53:25Z" - latency: 1.237736ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:52:25Z" - latency: 1.119505ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:51:25Z" - latency: 1.016327ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:50:25Z" - latency: 1.142949ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:49:25Z" - latency: 950.514µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:48:25Z" - latency: 1.30793ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:47:25Z" - latency: 1.374792ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:46:25Z" - latency: 764.804µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:45:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T20:26:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-207-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-207.ec2.internal uid: 6abe8693-aeae-43b0-b0f2-48c357271df9 resourceVersion: "48572" uid: 57def7e7-9323-4b7d-a18f-e7f48080e519 spec: sourcePod: network-check-source-dbd9cf844-gcvst targetEndpoint: ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-06T20:32:25Z" message: 'load-balancer-api-external: tcp connection to ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.269569ms message: 'load-balancer-api-external: tcp connection to ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:56:25Z" - latency: 8.264541ms message: 'load-balancer-api-external: resolved host name ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T20:56:25Z" - latency: 4.84105ms message: 'load-balancer-api-external: tcp connection to ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:55:25Z" - latency: 6.583989ms message: 'load-balancer-api-external: resolved host name ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T20:55:25Z" - latency: 3.851403ms message: 'load-balancer-api-external: tcp connection to ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:54:25Z" - latency: 6.844936ms message: 'load-balancer-api-external: resolved host name ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T20:54:25Z" - latency: 4.300125ms message: 'load-balancer-api-external: tcp connection to ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:53:25Z" - latency: 7.395148ms message: 'load-balancer-api-external: resolved host name ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T20:53:25Z" - latency: 4.708656ms message: 'load-balancer-api-external: tcp connection to ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:52:25Z" - latency: 7.093301ms message: 'load-balancer-api-external: resolved host name ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T20:52:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T20:26:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-207-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-207.ec2.internal uid: 6abe8693-aeae-43b0-b0f2-48c357271df9 resourceVersion: "48571" uid: 2e06b6ae-4d10-49cb-b051-354b0854006c spec: sourcePod: network-check-source-dbd9cf844-gcvst targetEndpoint: ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-06T20:32:25Z" message: 'load-balancer-api-internal: tcp connection to ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.276968ms message: 'load-balancer-api-internal: tcp connection to ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:56:25Z" - latency: 8.179244ms message: 'load-balancer-api-internal: resolved host name ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T20:56:25Z" - latency: 4.854498ms message: 'load-balancer-api-internal: tcp connection to ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:55:25Z" - latency: 6.639606ms message: 'load-balancer-api-internal: resolved host name ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T20:55:25Z" - latency: 3.689406ms message: 'load-balancer-api-internal: tcp connection to ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:54:25Z" - latency: 6.766387ms message: 'load-balancer-api-internal: resolved host name ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T20:54:25Z" - latency: 4.292411ms message: 'load-balancer-api-internal: tcp connection to ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:53:25Z" - latency: 7.451693ms message: 'load-balancer-api-internal: resolved host name ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T20:53:25Z" - latency: 4.751072ms message: 'load-balancer-api-internal: tcp connection to ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:52:25Z" - latency: 7.027607ms message: 'load-balancer-api-internal: resolved host name ad90a531ad40048c4b3be81f2aa47fc2-d456f9694e92738f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T20:52:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T20:26:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-207-to-network-check-target-ip-10-0-131-207 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-207.ec2.internal uid: 6abe8693-aeae-43b0-b0f2-48c357271df9 resourceVersion: "46527" uid: 04683f44-5a03-4763-8cad-1ae64c766647 spec: sourcePod: network-check-source-dbd9cf844-gcvst targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-06T20:33:25Z" message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.558334ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:54:25Z" - latency: 1.465911ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:53:25Z" - latency: 907.229µs message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:52:25Z" - latency: 1.497668ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:51:25Z" - latency: 1.387233ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:50:25Z" - latency: 826.364µs message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:49:25Z" - latency: 932.225µs message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:48:25Z" - latency: 1.18463ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:47:25Z" - latency: 977.442µs message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:46:25Z" - latency: 947.602µs message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:45:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T20:26:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-207-to-network-check-target-ip-10-0-131-27 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-207.ec2.internal uid: 6abe8693-aeae-43b0-b0f2-48c357271df9 resourceVersion: "46526" uid: 5d9d4ddb-8c67-4deb-852a-9b67e80c8b3b spec: sourcePod: network-check-source-dbd9cf844-gcvst targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-06T20:33:25Z" message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.071345ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:54:25Z" - latency: 1.787545ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:53:25Z" - latency: 1.779979ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:52:25Z" - latency: 1.968704ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:51:25Z" - latency: 2.051887ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:50:25Z" - latency: 1.720294ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:49:25Z" - latency: 1.813076ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:48:25Z" - latency: 2.101203ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:47:25Z" - latency: 1.909469ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:46:25Z" - latency: 2.028366ms message: 'network-check-target-ip-10-0-131-27: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:45:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T20:26:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-207-to-network-check-target-ip-10-0-140-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-207.ec2.internal uid: 6abe8693-aeae-43b0-b0f2-48c357271df9 resourceVersion: "46528" uid: 50e217d9-a808-4d5a-935a-1e0689b8dc2c spec: sourcePod: network-check-source-dbd9cf844-gcvst targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-06T20:33:25Z" message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.132053ms message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:54:25Z" - latency: 2.178728ms message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:53:25Z" - latency: 2.253348ms message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:52:25Z" - latency: 2.114138ms message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:51:25Z" - latency: 2.147406ms message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:50:25Z" - latency: 2.093267ms message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:49:25Z" - latency: 2.098539ms message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:48:25Z" - latency: 2.355638ms message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:47:25Z" - latency: 2.117541ms message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:46:25Z" - latency: 2.199491ms message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:45:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T20:26:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-207-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-207.ec2.internal uid: 6abe8693-aeae-43b0-b0f2-48c357271df9 resourceVersion: "48570" uid: e2524bab-bb7e-4159-9088-6bf1f5c0170c spec: sourcePod: network-check-source-dbd9cf844-gcvst targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-06T20:32:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 885.287µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:56:25Z" - latency: 1.72253ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T20:56:25Z" - latency: 1.216364ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:55:25Z" - latency: 1.797962ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T20:55:25Z" - latency: 900.641µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:54:25Z" - latency: 1.869585ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T20:54:25Z" - latency: 795.953µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:53:25Z" - latency: 1.859018ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T20:53:25Z" - latency: 927.671µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T20:52:25Z" - latency: 1.748871ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T20:52:25Z" kind: List metadata: resourceVersion: ""