apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:09:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-149-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-149.ec2.internal uid: 53a18955-fb7c-43a1-babd-17a0c3cba170 resourceVersion: "74454" uid: 6922fc08-3868-4fbe-8454-099ffeac206c spec: sourcePod: network-check-source-7d88cb55d8-phqdx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T20:16:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.268158ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:58:23Z" - latency: 1.034153ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:57:23Z" - latency: 1.210578ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:56:23Z" - latency: 1.033273ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:55:23Z" - latency: 1.374511ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:54:23Z" - latency: 862.546µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:53:23Z" - latency: 928.012µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:52:23Z" - latency: 1.609447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:51:23Z" - latency: 1.202639ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:50:23Z" - latency: 968.319µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:49:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:09:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-149-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-149.ec2.internal uid: 53a18955-fb7c-43a1-babd-17a0c3cba170 resourceVersion: "72095" uid: f32ff541-1115-4c42-b629-5aed9b82569a spec: sourcePod: network-check-source-7d88cb55d8-phqdx targetEndpoint: aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T20:15:23Z" message: 'load-balancer-api-external: tcp connection to aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.017335ms message: 'load-balancer-api-external: tcp connection to aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:57:23Z" - latency: 8.507314ms message: 'load-balancer-api-external: resolved host name aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T20:57:23Z" - latency: 3.603861ms message: 'load-balancer-api-external: tcp connection to aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:56:23Z" - latency: 7.529526ms message: 'load-balancer-api-external: resolved host name aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T20:56:23Z" - latency: 4.210939ms message: 'load-balancer-api-external: tcp connection to aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:55:23Z" - latency: 7.341548ms message: 'load-balancer-api-external: resolved host name aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T20:55:23Z" - latency: 4.985645ms message: 'load-balancer-api-external: tcp connection to aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:54:23Z" - latency: 9.037718ms message: 'load-balancer-api-external: resolved host name aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T20:54:23Z" - latency: 6.893169ms message: 'load-balancer-api-external: tcp connection to aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:53:23Z" - latency: 12.995693ms message: 'load-balancer-api-external: resolved host name aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T20:53:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:09:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-149-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-149.ec2.internal uid: 53a18955-fb7c-43a1-babd-17a0c3cba170 resourceVersion: "72094" uid: edec19b7-856b-4ad8-be71-e68831bad8a2 spec: sourcePod: network-check-source-7d88cb55d8-phqdx targetEndpoint: aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T20:15:23Z" message: 'load-balancer-api-internal: tcp connection to aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.94473ms message: 'load-balancer-api-internal: tcp connection to aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:57:23Z" - latency: 8.539419ms message: 'load-balancer-api-internal: resolved host name aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T20:57:23Z" - latency: 3.596148ms message: 'load-balancer-api-internal: tcp connection to aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:56:23Z" - latency: 7.652267ms message: 'load-balancer-api-internal: resolved host name aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T20:56:23Z" - latency: 4.277392ms message: 'load-balancer-api-internal: tcp connection to aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:55:23Z" - latency: 7.302335ms message: 'load-balancer-api-internal: resolved host name aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T20:55:23Z" - latency: 4.89421ms message: 'load-balancer-api-internal: tcp connection to aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:54:23Z" - latency: 9.111594ms message: 'load-balancer-api-internal: resolved host name aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T20:54:23Z" - latency: 3.345502ms message: 'load-balancer-api-internal: tcp connection to aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:53:23Z" - latency: 12.91408ms message: 'load-balancer-api-internal: resolved host name aa04a3529bbe041f882926e07e6b2072-976e8a1a06e3ea98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T20:53:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:09:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-149-to-network-check-target-ip-10-0-128-149 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-149.ec2.internal uid: 53a18955-fb7c-43a1-babd-17a0c3cba170 resourceVersion: "74451" uid: 648d07bb-8758-4c61-a7f0-87a033cd78a3 spec: sourcePod: network-check-source-7d88cb55d8-phqdx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T20:16:23Z" message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.12715ms message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:58:23Z" - latency: 1.214345ms message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:57:23Z" - latency: 1.379279ms message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:56:23Z" - latency: 1.039147ms message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:55:23Z" - latency: 967.51µs message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:54:23Z" - latency: 885.241µs message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:53:23Z" - latency: 1.049869ms message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:52:23Z" - latency: 1.076462ms message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:51:23Z" - latency: 1.245902ms message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:50:23Z" - latency: 1.326087ms message: 'network-check-target-ip-10-0-128-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:49:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:09:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-149-to-network-check-target-ip-10-0-133-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-149.ec2.internal uid: 53a18955-fb7c-43a1-babd-17a0c3cba170 resourceVersion: "74452" uid: 78fcacb2-fe39-46b7-8d4d-19932fa173d4 spec: sourcePod: network-check-source-7d88cb55d8-phqdx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T20:16:23Z" message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.334493ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:58:23Z" - latency: 2.441469ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:57:23Z" - latency: 2.358424ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:56:23Z" - latency: 1.974532ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:55:23Z" - latency: 2.301523ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:54:23Z" - latency: 2.352358ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:53:23Z" - latency: 2.208408ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:52:23Z" - latency: 2.219286ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:51:23Z" - latency: 2.136763ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:50:23Z" - latency: 2.279961ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:49:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:09:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-149-to-network-check-target-ip-10-0-138-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-149.ec2.internal uid: 53a18955-fb7c-43a1-babd-17a0c3cba170 resourceVersion: "74453" uid: 2e6f9f46-4640-4d3b-b7c5-fbddda6e8aed spec: sourcePod: network-check-source-7d88cb55d8-phqdx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T20:16:23Z" message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.730765ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:58:23Z" - latency: 2.429957ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:57:23Z" - latency: 2.262392ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:56:23Z" - latency: 1.979972ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:55:23Z" - latency: 2.155607ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:54:23Z" - latency: 1.867857ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:53:23Z" - latency: 2.323348ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:52:23Z" - latency: 2.652033ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:51:23Z" - latency: 2.52671ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:50:23Z" - latency: 2.158646ms message: 'network-check-target-ip-10-0-138-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:49:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:09:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-149-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-149.ec2.internal uid: 53a18955-fb7c-43a1-babd-17a0c3cba170 resourceVersion: "72092" uid: c2356e57-fc3d-43dc-8019-bc04449da49b spec: sourcePod: network-check-source-7d88cb55d8-phqdx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T20:15:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.16757ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:57:23Z" - latency: 1.814453ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T20:57:23Z" - latency: 1.108404ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:56:23Z" - latency: 2.388005ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T20:56:23Z" - latency: 1.072662ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:55:23Z" - latency: 1.864343ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T20:55:23Z" - latency: 1.211845ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:54:23Z" - latency: 1.913174ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T20:54:23Z" - latency: 938.789µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:53:23Z" - latency: 1.936243ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T20:53:23Z" kind: List metadata: resourceVersion: ""