apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T21:35:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-134-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-134.ec2.internal uid: 8b1eda8b-30f0-414e-9a97-5b1b646c1805 resourceVersion: "46691" uid: 53d6b73e-9117-460a-8b17-99666c2a5485 spec: sourcePod: network-check-source-dbd9cf844-wspxj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-03T21:42:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.874912ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:03:50Z" - latency: 1.12074ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:02:50Z" - latency: 914.432µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:01:50Z" - latency: 1.233651ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:00:50Z" - latency: 1.256099ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:59:50Z" - latency: 1.159889ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:58:50Z" - latency: 1.286374ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:57:50Z" - latency: 1.269577ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:56:50Z" - latency: 1.052717ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:55:50Z" - latency: 790.324µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:54:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T21:35:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-134-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-134.ec2.internal uid: 8b1eda8b-30f0-414e-9a97-5b1b646c1805 resourceVersion: "48801" uid: d15b9c27-672e-4753-b507-9d109846053e spec: sourcePod: network-check-source-dbd9cf844-wspxj targetEndpoint: a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T21:41:51Z" message: 'load-balancer-api-external: tcp connection to a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.66015ms message: 'load-balancer-api-external: tcp connection to a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:05:51Z" - latency: 9.07265ms message: 'load-balancer-api-external: resolved host name a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T22:05:50Z" - latency: 4.680664ms message: 'load-balancer-api-external: tcp connection to a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:04:51Z" - latency: 8.253643ms message: 'load-balancer-api-external: resolved host name a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T22:04:50Z" - latency: 3.633819ms message: 'load-balancer-api-external: tcp connection to a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:03:51Z" - latency: 9.651385ms message: 'load-balancer-api-external: resolved host name a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T22:03:50Z" - latency: 4.390319ms message: 'load-balancer-api-external: tcp connection to a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:02:51Z" - latency: 10.172063ms message: 'load-balancer-api-external: resolved host name a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T22:02:50Z" - latency: 4.931415ms message: 'load-balancer-api-external: tcp connection to a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:01:51Z" - latency: 8.411053ms message: 'load-balancer-api-external: resolved host name a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T22:01:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T21:35:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-134-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-134.ec2.internal uid: 8b1eda8b-30f0-414e-9a97-5b1b646c1805 resourceVersion: "48800" uid: bf987bdd-3e34-4dc0-975a-61be6c404734 spec: sourcePod: network-check-source-dbd9cf844-wspxj targetEndpoint: a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T21:41:51Z" message: 'load-balancer-api-internal: tcp connection to a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.717515ms message: 'load-balancer-api-internal: tcp connection to a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:05:51Z" - latency: 9.023143ms message: 'load-balancer-api-internal: resolved host name a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T22:05:50Z" - latency: 4.718235ms message: 'load-balancer-api-internal: tcp connection to a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:04:51Z" - latency: 8.22372ms message: 'load-balancer-api-internal: resolved host name a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T22:04:50Z" - latency: 3.619554ms message: 'load-balancer-api-internal: tcp connection to a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:03:51Z" - latency: 9.617622ms message: 'load-balancer-api-internal: resolved host name a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T22:03:50Z" - latency: 4.400211ms message: 'load-balancer-api-internal: tcp connection to a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:02:51Z" - latency: 10.120184ms message: 'load-balancer-api-internal: resolved host name a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T22:02:50Z" - latency: 5.1953ms message: 'load-balancer-api-internal: tcp connection to a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:01:51Z" - latency: 8.341046ms message: 'load-balancer-api-internal: resolved host name a2d68d8b6193346cfa60617d97970a40-bf8349196402b573.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T22:01:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T21:35:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-134-to-network-check-target-ip-10-0-137-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-134.ec2.internal uid: 8b1eda8b-30f0-414e-9a97-5b1b646c1805 resourceVersion: "46690" uid: 0a5629cb-b81a-4f40-a6c1-80b1fbfae8cb spec: sourcePod: network-check-source-dbd9cf844-wspxj targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-03T21:42:50Z" message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.282679ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:03:50Z" - latency: 2.33979ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:02:50Z" - latency: 2.064447ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:01:50Z" - latency: 2.320694ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:00:50Z" - latency: 2.15738ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:59:50Z" - latency: 2.852385ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:58:50Z" - latency: 2.163954ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:57:50Z" - latency: 2.394434ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:56:50Z" - latency: 2.183581ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:55:50Z" - latency: 2.317685ms message: 'network-check-target-ip-10-0-137-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:54:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T21:35:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-134-to-network-check-target-ip-10-0-140-77 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-134.ec2.internal uid: 8b1eda8b-30f0-414e-9a97-5b1b646c1805 resourceVersion: "46689" uid: 127f0b24-c35a-4d2b-ac09-ff02a32c7e4a spec: sourcePod: network-check-source-dbd9cf844-wspxj targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-03T21:42:50Z" message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.000784ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:03:50Z" - latency: 2.148654ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:02:50Z" - latency: 2.017275ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:01:50Z" - latency: 1.916439ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:00:50Z" - latency: 2.133372ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:59:50Z" - latency: 1.928659ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:58:50Z" - latency: 2.14707ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:57:50Z" - latency: 1.969192ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:56:50Z" - latency: 2.100771ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:55:50Z" - latency: 2.109373ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:54:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T21:35:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-134-to-network-check-target-ip-10-0-141-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-134.ec2.internal uid: 8b1eda8b-30f0-414e-9a97-5b1b646c1805 resourceVersion: "46688" uid: 1cf8c595-a0ff-4d4f-a647-d39c5ba5cc0f spec: sourcePod: network-check-source-dbd9cf844-wspxj targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-03T21:42:50Z" message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.007855ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:03:50Z" - latency: 1.398435ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:02:50Z" - latency: 906.861µs message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:01:50Z" - latency: 875.256µs message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:00:50Z" - latency: 1.091315ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:59:50Z" - latency: 2.031833ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:58:50Z" - latency: 979.469µs message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:57:50Z" - latency: 1.155805ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:56:50Z" - latency: 1.686612ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:55:50Z" - latency: 1.384492ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:54:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T21:35:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-134-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-134.ec2.internal uid: 8b1eda8b-30f0-414e-9a97-5b1b646c1805 resourceVersion: "48799" uid: 0f14abc5-1daa-4289-b296-43a5b0628af2 spec: sourcePod: network-check-source-dbd9cf844-wspxj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-03T21:41:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 960.955µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:05:50Z" - latency: 1.70547ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T22:05:50Z" - latency: 803.03µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:04:50Z" - latency: 1.872313ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T22:04:50Z" - latency: 793.811µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:03:50Z" - latency: 1.905603ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T22:03:50Z" - latency: 1.055657ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:02:50Z" - latency: 2.337564ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T22:02:50Z" - latency: 1.044506ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T22:01:50Z" - latency: 2.376367ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T22:01:50Z" kind: List metadata: resourceVersion: ""