apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:26:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-252-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-252.ec2.internal uid: 59c4f29f-5401-4da3-b216-ad7f0d70f1df resourceVersion: "32308" uid: 2cae56be-b626-4ef6-bd21-741ebaa6573b spec: sourcePod: network-check-source-56499946bc-sn7px targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-01T19:33:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 955.911µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:08:18Z" - latency: 1.116837ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:07:18Z" - latency: 1.182512ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:06:18Z" - latency: 1.049722ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:05:18Z" - latency: 1.188338ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:04:18Z" - latency: 1.115987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:03:18Z" - latency: 1.149716ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:02:18Z" - latency: 975.113µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:01:18Z" - latency: 848.185µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:00:18Z" - latency: 1.099637ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:59:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:26:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-252-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-252.ec2.internal uid: 59c4f29f-5401-4da3-b216-ad7f0d70f1df resourceVersion: "32309" uid: cc4fb3fd-eb63-45fb-8f0a-f708f63dd7e7 spec: sourcePod: network-check-source-56499946bc-sn7px targetEndpoint: a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T19:32:18Z" message: 'load-balancer-api-external: tcp connection to a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.768582ms message: 'load-balancer-api-external: tcp connection to a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:08:18Z" - latency: 8.572ms message: 'load-balancer-api-external: resolved host name a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T20:08:18Z" - latency: 5.069421ms message: 'load-balancer-api-external: tcp connection to a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:07:18Z" - latency: 8.475825ms message: 'load-balancer-api-external: resolved host name a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T20:07:18Z" - latency: 5.151834ms message: 'load-balancer-api-external: tcp connection to a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:06:18Z" - latency: 8.489846ms message: 'load-balancer-api-external: resolved host name a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T20:06:18Z" - latency: 6.023755ms message: 'load-balancer-api-external: tcp connection to a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:05:18Z" - latency: 10.638195ms message: 'load-balancer-api-external: resolved host name a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T20:05:18Z" - latency: 4.897057ms message: 'load-balancer-api-external: tcp connection to a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:04:18Z" - latency: 8.674931ms message: 'load-balancer-api-external: resolved host name a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T20:04:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:26:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-252-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-252.ec2.internal uid: 59c4f29f-5401-4da3-b216-ad7f0d70f1df resourceVersion: "32310" uid: 86d642f4-a7ef-46a5-a2ba-20102d4e0cdb spec: sourcePod: network-check-source-56499946bc-sn7px targetEndpoint: a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T19:32:18Z" message: 'load-balancer-api-internal: tcp connection to a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.76624ms message: 'load-balancer-api-internal: tcp connection to a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:08:18Z" - latency: 8.519831ms message: 'load-balancer-api-internal: resolved host name a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T20:08:18Z" - latency: 5.028216ms message: 'load-balancer-api-internal: tcp connection to a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:07:18Z" - latency: 8.502978ms message: 'load-balancer-api-internal: resolved host name a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T20:07:18Z" - latency: 4.076955ms message: 'load-balancer-api-internal: tcp connection to a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:06:18Z" - latency: 8.479155ms message: 'load-balancer-api-internal: resolved host name a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T20:06:18Z" - latency: 5.53392ms message: 'load-balancer-api-internal: tcp connection to a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:05:18Z" - latency: 10.711705ms message: 'load-balancer-api-internal: resolved host name a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T20:05:18Z" - latency: 4.513159ms message: 'load-balancer-api-internal: tcp connection to a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:04:18Z" - latency: 8.808266ms message: 'load-balancer-api-internal: resolved host name a7cb2041007134af78754989539e199d-32a54d10f582c877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T20:04:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:26:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-252-to-network-check-target-ip-10-0-129-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-252.ec2.internal uid: 59c4f29f-5401-4da3-b216-ad7f0d70f1df resourceVersion: "32306" uid: c5b9e881-9437-4211-b588-3983f459691e spec: sourcePod: network-check-source-56499946bc-sn7px targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-01T19:33:18Z" message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.248628ms message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:08:18Z" - latency: 2.333654ms message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:07:18Z" - latency: 2.334333ms message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:06:18Z" - latency: 2.175992ms message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:05:18Z" - latency: 2.385906ms message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:04:18Z" - latency: 2.204815ms message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:03:18Z" - latency: 2.117027ms message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:02:18Z" - latency: 6.905959ms message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:01:18Z" - latency: 2.256874ms message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:00:18Z" - latency: 2.021756ms message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:59:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:26:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-252-to-network-check-target-ip-10-0-134-212 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-252.ec2.internal uid: 59c4f29f-5401-4da3-b216-ad7f0d70f1df resourceVersion: "32305" uid: 0a58005c-5d15-463e-95d1-04d057c8d197 spec: sourcePod: network-check-source-56499946bc-sn7px targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-01T19:33:18Z" message: 'network-check-target-ip-10-0-134-212: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.265532ms message: 'network-check-target-ip-10-0-134-212: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:08:18Z" - latency: 2.152469ms message: 'network-check-target-ip-10-0-134-212: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:07:18Z" - latency: 2.481589ms message: 'network-check-target-ip-10-0-134-212: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:06:18Z" - latency: 2.161487ms message: 'network-check-target-ip-10-0-134-212: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:05:18Z" - latency: 1.95968ms message: 'network-check-target-ip-10-0-134-212: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:04:18Z" - latency: 2.216416ms message: 'network-check-target-ip-10-0-134-212: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:03:18Z" - latency: 2.412208ms message: 'network-check-target-ip-10-0-134-212: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:02:18Z" - latency: 2.251084ms message: 'network-check-target-ip-10-0-134-212: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:01:18Z" - latency: 2.128447ms message: 'network-check-target-ip-10-0-134-212: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:00:18Z" - latency: 2.290066ms message: 'network-check-target-ip-10-0-134-212: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:59:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:26:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-252-to-network-check-target-ip-10-0-138-252 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-252.ec2.internal uid: 59c4f29f-5401-4da3-b216-ad7f0d70f1df resourceVersion: "32304" uid: 857b97c9-d089-44fa-8d28-fb58677512ea spec: sourcePod: network-check-source-56499946bc-sn7px targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T19:33:18Z" message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.048072ms message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:08:18Z" - latency: 890.067µs message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:07:18Z" - latency: 1.673018ms message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:06:18Z" - latency: 982.248µs message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:05:18Z" - latency: 1.882204ms message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:04:18Z" - latency: 915.56µs message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:03:18Z" - latency: 767.86µs message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:02:18Z" - latency: 830.029µs message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:01:18Z" - latency: 929.1µs message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:00:18Z" - latency: 1.261213ms message: 'network-check-target-ip-10-0-138-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:59:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:26:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-252-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-252.ec2.internal uid: 59c4f29f-5401-4da3-b216-ad7f0d70f1df resourceVersion: "32307" uid: a62dee88-2941-43c9-b634-983571cbfab2 spec: sourcePod: network-check-source-56499946bc-sn7px targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-01T19:32:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.120156ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:08:18Z" - latency: 1.911366ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T20:08:18Z" - latency: 815.428µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:07:18Z" - latency: 1.673543ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T20:07:18Z" - latency: 967.257µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:06:18Z" - latency: 1.641549ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T20:06:18Z" - latency: 938.02µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:05:18Z" - latency: 2.068945ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T20:05:18Z" - latency: 834.03µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T20:04:18Z" - latency: 2.266259ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T20:04:18Z" kind: List metadata: resourceVersion: ""