apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:26:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-184-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-184.ec2.internal uid: af95e36b-dd32-468d-99b3-98f5610d2dfb resourceVersion: "47796" uid: 3914fa21-ab8e-4613-a8db-9a4b5c4d08d2 spec: sourcePod: network-check-source-7f44b6dd87-2f94r targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-25T11:33:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 985.666µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:08:44Z" - latency: 1.289141ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:07:44Z" - latency: 851.89µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:06:44Z" - latency: 1.208537ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:05:44Z" - latency: 686.907µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:04:44Z" - latency: 769.276µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:03:44Z" - latency: 11.366182ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:02:44Z" - latency: 841.758µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:01:44Z" - latency: 819.246µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:00:44Z" - latency: 1.30651ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:59:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:26:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-184-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-184.ec2.internal uid: af95e36b-dd32-468d-99b3-98f5610d2dfb resourceVersion: "47797" uid: c8e65e63-8b8f-47e8-abe9-1b06b9a7e81e spec: sourcePod: network-check-source-7f44b6dd87-2f94r targetEndpoint: a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T11:32:44Z" message: 'load-balancer-api-external: tcp connection to a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.630076ms message: 'load-balancer-api-external: tcp connection to a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:08:44Z" - latency: 6.90349ms message: 'load-balancer-api-external: resolved host name a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:08:44Z" - latency: 4.891972ms message: 'load-balancer-api-external: tcp connection to a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:07:44Z" - latency: 6.665403ms message: 'load-balancer-api-external: resolved host name a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:07:44Z" - latency: 3.494774ms message: 'load-balancer-api-external: tcp connection to a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:06:44Z" - latency: 6.275936ms message: 'load-balancer-api-external: resolved host name a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:06:44Z" - latency: 5.86122ms message: 'load-balancer-api-external: tcp connection to a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:05:44Z" - latency: 6.308172ms message: 'load-balancer-api-external: resolved host name a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:05:44Z" - latency: 4.080147ms message: 'load-balancer-api-external: tcp connection to a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:04:44Z" - latency: 6.664106ms message: 'load-balancer-api-external: resolved host name a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:04:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:26:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-184-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-184.ec2.internal uid: af95e36b-dd32-468d-99b3-98f5610d2dfb resourceVersion: "47798" uid: 6150848a-4a3f-4a1d-ab84-d927858d4db5 spec: sourcePod: network-check-source-7f44b6dd87-2f94r targetEndpoint: a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T11:32:44Z" message: 'load-balancer-api-internal: tcp connection to a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.605579ms message: 'load-balancer-api-internal: tcp connection to a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:08:44Z" - latency: 6.971864ms message: 'load-balancer-api-internal: resolved host name a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:08:44Z" - latency: 4.887397ms message: 'load-balancer-api-internal: tcp connection to a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:07:44Z" - latency: 6.567097ms message: 'load-balancer-api-internal: resolved host name a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:07:44Z" - latency: 3.457337ms message: 'load-balancer-api-internal: tcp connection to a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:06:44Z" - latency: 6.313203ms message: 'load-balancer-api-internal: resolved host name a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:06:44Z" - latency: 4.30175ms message: 'load-balancer-api-internal: tcp connection to a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:05:44Z" - latency: 6.22502ms message: 'load-balancer-api-internal: resolved host name a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:05:44Z" - latency: 4.047162ms message: 'load-balancer-api-internal: tcp connection to a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:04:44Z" - latency: 6.697377ms message: 'load-balancer-api-internal: resolved host name a94815d5b051c4e23bf3ca3484918e15-4525d54215dd310c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:04:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:26:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-184-to-network-check-target-ip-10-0-128-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-184.ec2.internal uid: af95e36b-dd32-468d-99b3-98f5610d2dfb resourceVersion: "47794" uid: 0a1f25fa-5407-46eb-9efa-ef825f9671b3 spec: sourcePod: network-check-source-7f44b6dd87-2f94r targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-25T11:33:44Z" message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.437054ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:08:44Z" - latency: 2.278299ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:07:44Z" - latency: 2.271903ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:06:44Z" - latency: 1.95011ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:05:44Z" - latency: 2.20872ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:04:44Z" - latency: 2.243006ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:03:44Z" - latency: 5.727148ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:02:44Z" - latency: 2.039104ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:01:44Z" - latency: 2.429152ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:00:44Z" - latency: 1.941471ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:59:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:26:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-184-to-network-check-target-ip-10-0-133-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-184.ec2.internal uid: af95e36b-dd32-468d-99b3-98f5610d2dfb resourceVersion: "47795" uid: 8da70f95-0ac0-4c6b-9a77-f8922f1201d4 spec: sourcePod: network-check-source-7f44b6dd87-2f94r targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T11:33:44Z" message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.513761ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:08:44Z" - latency: 2.418246ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:07:44Z" - latency: 2.195346ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:06:44Z" - latency: 2.218844ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:05:44Z" - latency: 2.33571ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:04:44Z" - latency: 2.24783ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:03:44Z" - latency: 4.412481ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:02:44Z" - latency: 2.121695ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:01:44Z" - latency: 2.633013ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:00:44Z" - latency: 2.41255ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:59:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:26:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-184-to-network-check-target-ip-10-0-134-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-184.ec2.internal uid: af95e36b-dd32-468d-99b3-98f5610d2dfb resourceVersion: "47792" uid: cf5a1f4f-253d-4ee3-86b9-dbf345c8eba3 spec: sourcePod: network-check-source-7f44b6dd87-2f94r targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T11:33:44Z" message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.030241ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:08:44Z" - latency: 793.646µs message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:07:44Z" - latency: 1.586525ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:06:44Z" - latency: 757.865µs message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:05:44Z" - latency: 944.576µs message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:04:44Z" - latency: 1.361441ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:03:44Z" - latency: 2.588221ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:02:44Z" - latency: 1.192771ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:01:44Z" - latency: 1.222646ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:00:44Z" - latency: 780.65µs message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T11:59:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T11:26:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-184-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-184.ec2.internal uid: af95e36b-dd32-468d-99b3-98f5610d2dfb resourceVersion: "47793" uid: 16153a79-a578-4e5a-8793-184abd78bf4f spec: sourcePod: network-check-source-7f44b6dd87-2f94r targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-25T11:32:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 727.384µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:08:44Z" - latency: 1.917286ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T12:08:44Z" - latency: 1.060738ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:07:44Z" - latency: 2.239297ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T12:07:44Z" - latency: 928.501µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:06:44Z" - latency: 1.751485ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T12:06:44Z" - latency: 850.734µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:05:44Z" - latency: 1.664491ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T12:05:44Z" - latency: 784.406µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:04:44Z" - latency: 1.669044ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T12:04:44Z" kind: List metadata: resourceVersion: ""