apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T22:32:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-206-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-206.ec2.internal uid: 9ad4786e-b1a6-4e42-97f9-d3d6290bed50 resourceVersion: "29332" uid: 430ceeb2-e288-48a5-9a7e-7886b4f0c04d spec: sourcePod: network-check-source-989f8b8dc-56fv7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T22:39:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.054781ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:46:40Z" - latency: 997.52µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:45:40Z" - latency: 1.20784ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:44:40Z" - latency: 1.049742ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:43:40Z" - latency: 1.528401ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:42:40Z" - latency: 1.219559ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:41:40Z" - latency: 839.072µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:40:40Z" - latency: 1.230164ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:39:40Z" - latency: 1.09759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:38:40Z" - latency: 1.074099ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:37:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T22:32:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-206-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-206.ec2.internal uid: 9ad4786e-b1a6-4e42-97f9-d3d6290bed50 resourceVersion: "32363" uid: f06d66fc-b718-4196-bc8f-b5d40de33817 spec: sourcePod: network-check-source-989f8b8dc-56fv7 targetEndpoint: afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T22:38:40Z" message: 'load-balancer-api-external: tcp connection to afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.373432ms message: 'load-balancer-api-external: tcp connection to afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:50:40Z" - latency: 8.602164ms message: 'load-balancer-api-external: resolved host name afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:50:40Z" - latency: 5.019098ms message: 'load-balancer-api-external: tcp connection to afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:49:40Z" - latency: 8.284518ms message: 'load-balancer-api-external: resolved host name afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:49:40Z" - latency: 5.09666ms message: 'load-balancer-api-external: tcp connection to afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:48:40Z" - latency: 8.524512ms message: 'load-balancer-api-external: resolved host name afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:48:40Z" - latency: 4.897081ms message: 'load-balancer-api-external: tcp connection to afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:47:40Z" - latency: 8.981151ms message: 'load-balancer-api-external: resolved host name afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:47:40Z" - latency: 5.789634ms message: 'load-balancer-api-external: tcp connection to afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:46:40Z" - latency: 8.765538ms message: 'load-balancer-api-external: resolved host name afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:46:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T22:32:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-206-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-206.ec2.internal uid: 9ad4786e-b1a6-4e42-97f9-d3d6290bed50 resourceVersion: "32362" uid: ed40f980-6f61-4764-a222-5da77f86b9e3 spec: sourcePod: network-check-source-989f8b8dc-56fv7 targetEndpoint: afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T22:38:40Z" message: 'load-balancer-api-internal: tcp connection to afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.270623ms message: 'load-balancer-api-internal: tcp connection to afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:50:40Z" - latency: 8.678585ms message: 'load-balancer-api-internal: resolved host name afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:50:40Z" - latency: 4.112208ms message: 'load-balancer-api-internal: tcp connection to afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:49:40Z" - latency: 8.409954ms message: 'load-balancer-api-internal: resolved host name afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:49:40Z" - latency: 5.083191ms message: 'load-balancer-api-internal: tcp connection to afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:48:40Z" - latency: 8.559188ms message: 'load-balancer-api-internal: resolved host name afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:48:40Z" - latency: 5.128277ms message: 'load-balancer-api-internal: tcp connection to afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:47:40Z" - latency: 8.927324ms message: 'load-balancer-api-internal: resolved host name afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:47:40Z" - latency: 5.218359ms message: 'load-balancer-api-internal: tcp connection to afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:46:40Z" - latency: 8.845641ms message: 'load-balancer-api-internal: resolved host name afab4f332edc74e80a8dad69cd1d0491-84fb88792cf1ace6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:46:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T22:32:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-206-to-network-check-target-ip-10-0-130-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-206.ec2.internal uid: 9ad4786e-b1a6-4e42-97f9-d3d6290bed50 resourceVersion: "29329" uid: b16981db-f24a-4840-92a9-b49b45432907 spec: sourcePod: network-check-source-989f8b8dc-56fv7 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T22:39:40Z" message: 'network-check-target-ip-10-0-130-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.209495ms message: 'network-check-target-ip-10-0-130-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:46:40Z" - latency: 858.785µs message: 'network-check-target-ip-10-0-130-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:45:40Z" - latency: 868.051µs message: 'network-check-target-ip-10-0-130-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:44:40Z" - latency: 765.269µs message: 'network-check-target-ip-10-0-130-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:43:40Z" - latency: 818.555µs message: 'network-check-target-ip-10-0-130-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:42:40Z" - latency: 794.425µs message: 'network-check-target-ip-10-0-130-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:41:40Z" - latency: 770.308µs message: 'network-check-target-ip-10-0-130-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:40:40Z" - latency: 1.03781ms message: 'network-check-target-ip-10-0-130-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:39:40Z" - latency: 914.759µs message: 'network-check-target-ip-10-0-130-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:38:40Z" - latency: 1.04223ms message: 'network-check-target-ip-10-0-130-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:37:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T22:32:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-206-to-network-check-target-ip-10-0-136-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-206.ec2.internal uid: 9ad4786e-b1a6-4e42-97f9-d3d6290bed50 resourceVersion: "29330" uid: 7b9d1519-f201-4b91-b017-3cb0584e26fe spec: sourcePod: network-check-source-989f8b8dc-56fv7 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T22:39:40Z" message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.138235ms message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:46:40Z" - latency: 2.07728ms message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:45:40Z" - latency: 1.807621ms message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:44:40Z" - latency: 1.779998ms message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:43:40Z" - latency: 2.069774ms message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:42:40Z" - latency: 2.02058ms message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:41:40Z" - latency: 1.777055ms message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:40:40Z" - latency: 1.925382ms message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:39:40Z" - latency: 1.899307ms message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:38:40Z" - latency: 2.354952ms message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:37:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T22:32:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-206-to-network-check-target-ip-10-0-139-240 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-206.ec2.internal uid: 9ad4786e-b1a6-4e42-97f9-d3d6290bed50 resourceVersion: "29331" uid: 2021c08c-a0f6-454f-9961-87921b94912a spec: sourcePod: network-check-source-989f8b8dc-56fv7 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T22:39:40Z" message: 'network-check-target-ip-10-0-139-240: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.656777ms message: 'network-check-target-ip-10-0-139-240: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:46:40Z" - latency: 2.02717ms message: 'network-check-target-ip-10-0-139-240: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:45:40Z" - latency: 2.392675ms message: 'network-check-target-ip-10-0-139-240: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:44:40Z" - latency: 2.206335ms message: 'network-check-target-ip-10-0-139-240: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:43:40Z" - latency: 2.330917ms message: 'network-check-target-ip-10-0-139-240: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:42:40Z" - latency: 2.421452ms message: 'network-check-target-ip-10-0-139-240: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:41:40Z" - latency: 1.92693ms message: 'network-check-target-ip-10-0-139-240: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:40:40Z" - latency: 2.170877ms message: 'network-check-target-ip-10-0-139-240: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:39:40Z" - latency: 1.880351ms message: 'network-check-target-ip-10-0-139-240: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:38:40Z" - latency: 2.256737ms message: 'network-check-target-ip-10-0-139-240: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:37:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T22:32:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-206-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-206.ec2.internal uid: 9ad4786e-b1a6-4e42-97f9-d3d6290bed50 resourceVersion: "32361" uid: 9cbd734a-c4d0-454f-93f7-e8d7eabd1ed5 spec: sourcePod: network-check-source-989f8b8dc-56fv7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T22:38:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 761.64µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:50:40Z" - latency: 2.109899ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T22:50:40Z" - latency: 1.23686ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:49:40Z" - latency: 1.973741ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T22:49:40Z" - latency: 761.095µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:48:40Z" - latency: 1.996642ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T22:48:40Z" - latency: 834.695µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:47:40Z" - latency: 2.187304ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T22:47:40Z" - latency: 886.722µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:46:40Z" - latency: 1.745988ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T22:46:40Z" kind: List metadata: resourceVersion: ""