apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T11:52:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-234-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-234.ec2.internal uid: fd96e5c9-c455-47c0-aafa-74eb4cc0735c resourceVersion: "31380" uid: d1f41001-9de9-4b8b-afcf-955038fef41e spec: sourcePod: network-check-source-dbd9cf844-zqqxt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T11:59:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 888.689µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:06:22Z" - latency: 996.578µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:05:22Z" - latency: 1.547429ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:04:22Z" - latency: 1.34264ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:03:22Z" - latency: 1.113903ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:02:22Z" - latency: 803.362µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:01:22Z" - latency: 775.405µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:00:22Z" - latency: 1.193233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:59:22Z" - latency: 1.329283ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:58:22Z" - latency: 833.653µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T11:52:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-234-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-234.ec2.internal uid: fd96e5c9-c455-47c0-aafa-74eb4cc0735c resourceVersion: "35075" uid: f9933571-5439-4612-a1b1-96847bac3a16 spec: sourcePod: network-check-source-dbd9cf844-zqqxt targetEndpoint: a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T11:58:22Z" message: 'load-balancer-api-external: tcp connection to a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.803051ms message: 'load-balancer-api-external: tcp connection to a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:10:22Z" - latency: 6.867306ms message: 'load-balancer-api-external: resolved host name a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:10:22Z" - latency: 5.093595ms message: 'load-balancer-api-external: tcp connection to a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:09:22Z" - latency: 7.697092ms message: 'load-balancer-api-external: resolved host name a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:09:22Z" - latency: 5.349559ms message: 'load-balancer-api-external: tcp connection to a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:08:22Z" - latency: 6.297595ms message: 'load-balancer-api-external: resolved host name a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:08:22Z" - latency: 5.325154ms message: 'load-balancer-api-external: tcp connection to a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:07:22Z" - latency: 7.174436ms message: 'load-balancer-api-external: resolved host name a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:07:22Z" - latency: 4.835281ms message: 'load-balancer-api-external: tcp connection to a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:06:22Z" - latency: 7.209509ms message: 'load-balancer-api-external: resolved host name a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:06:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T11:52:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-234-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-234.ec2.internal uid: fd96e5c9-c455-47c0-aafa-74eb4cc0735c resourceVersion: "35076" uid: 800bd939-75ce-4af1-b5dd-ae45e87403cf spec: sourcePod: network-check-source-dbd9cf844-zqqxt targetEndpoint: a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T11:58:22Z" message: 'load-balancer-api-internal: tcp connection to a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.853119ms message: 'load-balancer-api-internal: tcp connection to a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:10:22Z" - latency: 6.956844ms message: 'load-balancer-api-internal: resolved host name a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:10:22Z" - latency: 5.066234ms message: 'load-balancer-api-internal: tcp connection to a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:09:22Z" - latency: 7.757278ms message: 'load-balancer-api-internal: resolved host name a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:09:22Z" - latency: 5.328491ms message: 'load-balancer-api-internal: tcp connection to a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:08:22Z" - latency: 6.436758ms message: 'load-balancer-api-internal: resolved host name a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:08:22Z" - latency: 5.334765ms message: 'load-balancer-api-internal: tcp connection to a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:07:22Z" - latency: 7.117062ms message: 'load-balancer-api-internal: resolved host name a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:07:22Z" - latency: 4.784084ms message: 'load-balancer-api-internal: tcp connection to a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:06:22Z" - latency: 7.301513ms message: 'load-balancer-api-internal: resolved host name a9f0baa54b94d4edebadaf58b19ec015-bb58da929352f243.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T12:06:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T11:52:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-234-to-network-check-target-ip-10-0-128-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-234.ec2.internal uid: fd96e5c9-c455-47c0-aafa-74eb4cc0735c resourceVersion: "31378" uid: 3edc2cf7-8138-4c04-959c-b38ccbc3bf70 spec: sourcePod: network-check-source-dbd9cf844-zqqxt targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T11:59:22Z" message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.294187ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:06:22Z" - latency: 1.658292ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:05:22Z" - latency: 1.824363ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:04:22Z" - latency: 2.457557ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:03:22Z" - latency: 2.245294ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:02:22Z" - latency: 1.938056ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:01:22Z" - latency: 1.631774ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:00:22Z" - latency: 1.729332ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:59:22Z" - latency: 2.105399ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:58:22Z" - latency: 1.602927ms message: 'network-check-target-ip-10-0-128-244: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T11:52:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-234-to-network-check-target-ip-10-0-132-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-234.ec2.internal uid: fd96e5c9-c455-47c0-aafa-74eb4cc0735c resourceVersion: "31377" uid: 85a27b86-b0af-4df6-8754-2155ddacb937 spec: sourcePod: network-check-source-dbd9cf844-zqqxt targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T11:59:22Z" message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.514131ms message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:06:22Z" - latency: 895.381µs message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:05:22Z" - latency: 987.267µs message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:04:22Z" - latency: 1.048584ms message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:03:22Z" - latency: 863.232µs message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:02:22Z" - latency: 915.379µs message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:01:22Z" - latency: 851.752µs message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:00:22Z" - latency: 756.159µs message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:59:22Z" - latency: 1.611623ms message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:58:22Z" - latency: 688.18µs message: 'network-check-target-ip-10-0-132-234: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T11:52:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-234-to-network-check-target-ip-10-0-133-240 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-234.ec2.internal uid: fd96e5c9-c455-47c0-aafa-74eb4cc0735c resourceVersion: "31379" uid: 25343855-dce0-49c0-898a-ad193d09c417 spec: sourcePod: network-check-source-dbd9cf844-zqqxt targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T11:59:22Z" message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.734134ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:06:22Z" - latency: 2.358899ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:05:22Z" - latency: 2.269846ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:04:22Z" - latency: 2.519589ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:03:22Z" - latency: 2.541172ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:02:22Z" - latency: 2.097167ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:01:22Z" - latency: 2.079736ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:00:22Z" - latency: 1.927891ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:59:22Z" - latency: 2.762041ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:58:22Z" - latency: 2.13722ms message: 'network-check-target-ip-10-0-133-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T11:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T11:52:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-234-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-234.ec2.internal uid: fd96e5c9-c455-47c0-aafa-74eb4cc0735c resourceVersion: "35074" uid: 337124c9-f0d8-4105-b774-3af46beb17bb spec: sourcePod: network-check-source-dbd9cf844-zqqxt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T11:58:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 915.918µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:10:22Z" - latency: 2.11714ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T12:10:22Z" - latency: 1.120461ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:09:22Z" - latency: 1.907998ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T12:09:22Z" - latency: 865.42µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:08:22Z" - latency: 1.763034ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T12:08:22Z" - latency: 1.04964ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:07:22Z" - latency: 1.690272ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T12:07:22Z" - latency: 1.018343ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T12:06:22Z" - latency: 2.260802ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T12:06:22Z" kind: List metadata: resourceVersion: ""