apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:25:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-120-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-120.ec2.internal uid: cb20af25-bd09-4e1c-9ee6-c5a2c24a69b2 resourceVersion: "52776" uid: b753f7b6-27f9-4347-9432-1c7228fb31e0 spec: sourcePod: network-check-source-685456655f-mbsl8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-08T16:32:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.324159ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:53:38Z" - latency: 2.102868ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:52:38Z" - latency: 864.574µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:51:38Z" - latency: 862.161µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:50:38Z" - latency: 1.051475ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:49:38Z" - latency: 1.305545ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:48:38Z" - latency: 1.194798ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:47:38Z" - latency: 1.111974ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:46:38Z" - latency: 881.049µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:45:38Z" - latency: 1.280339ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:44:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:25:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-120-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-120.ec2.internal uid: cb20af25-bd09-4e1c-9ee6-c5a2c24a69b2 resourceVersion: "54481" uid: 059b4ac9-db2e-4127-ac0f-949a9781d58f spec: sourcePod: network-check-source-685456655f-mbsl8 targetEndpoint: ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T16:31:38Z" message: 'load-balancer-api-external: tcp connection to ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.745672ms message: 'load-balancer-api-external: tcp connection to ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:55:38Z" - latency: 8.773562ms message: 'load-balancer-api-external: resolved host name ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:55:38Z" - latency: 4.752877ms message: 'load-balancer-api-external: tcp connection to ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:54:38Z" - latency: 7.509655ms message: 'load-balancer-api-external: resolved host name ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:54:38Z" - latency: 4.330027ms message: 'load-balancer-api-external: tcp connection to ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:53:38Z" - latency: 9.370323ms message: 'load-balancer-api-external: resolved host name ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:53:38Z" - latency: 4.145376ms message: 'load-balancer-api-external: tcp connection to ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:52:38Z" - latency: 9.619785ms message: 'load-balancer-api-external: resolved host name ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:52:38Z" - latency: 6.704568ms message: 'load-balancer-api-external: tcp connection to ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:51:38Z" - latency: 9.344689ms message: 'load-balancer-api-external: resolved host name ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:51:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:25:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-120-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-120.ec2.internal uid: cb20af25-bd09-4e1c-9ee6-c5a2c24a69b2 resourceVersion: "54480" uid: d4aa93f9-aa95-4737-a8ad-3e6b33162cdd spec: sourcePod: network-check-source-685456655f-mbsl8 targetEndpoint: ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T16:31:38Z" message: 'load-balancer-api-internal: tcp connection to ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.673232ms message: 'load-balancer-api-internal: tcp connection to ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:55:38Z" - latency: 8.89157ms message: 'load-balancer-api-internal: resolved host name ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:55:38Z" - latency: 4.691345ms message: 'load-balancer-api-internal: tcp connection to ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:54:38Z" - latency: 7.584649ms message: 'load-balancer-api-internal: resolved host name ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:54:38Z" - latency: 4.292042ms message: 'load-balancer-api-internal: tcp connection to ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:53:38Z" - latency: 9.472483ms message: 'load-balancer-api-internal: resolved host name ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:53:38Z" - latency: 4.511075ms message: 'load-balancer-api-internal: tcp connection to ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:52:38Z" - latency: 9.673268ms message: 'load-balancer-api-internal: resolved host name ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:52:38Z" - latency: 6.766435ms message: 'load-balancer-api-internal: tcp connection to ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:51:38Z" - latency: 9.447619ms message: 'load-balancer-api-internal: resolved host name ab68231969d1a443692ad7eeff24ab6d-ae8ffede84cc2d4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:51:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:25:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-120-to-network-check-target-ip-10-0-128-131 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-120.ec2.internal uid: cb20af25-bd09-4e1c-9ee6-c5a2c24a69b2 resourceVersion: "52774" uid: 72c5157a-30f3-4c98-8070-d70de99d8284 spec: sourcePod: network-check-source-685456655f-mbsl8 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-08T16:32:38Z" message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.964663ms message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:53:38Z" - latency: 1.712556ms message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:52:38Z" - latency: 2.000061ms message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:51:38Z" - latency: 1.919549ms message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:50:38Z" - latency: 2.374798ms message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:49:38Z" - latency: 2.509217ms message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:48:38Z" - latency: 2.425007ms message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:47:38Z" - latency: 3.197536ms message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:46:38Z" - latency: 2.710643ms message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:45:38Z" - latency: 2.123036ms message: 'network-check-target-ip-10-0-128-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:44:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:25:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-120-to-network-check-target-ip-10-0-133-120 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-120.ec2.internal uid: cb20af25-bd09-4e1c-9ee6-c5a2c24a69b2 resourceVersion: "52773" uid: 25a3da57-9b49-473a-988c-95edeb5436d2 spec: sourcePod: network-check-source-685456655f-mbsl8 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-08T16:32:38Z" message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 901.184µs message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:53:38Z" - latency: 944.355µs message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:52:38Z" - latency: 871.429µs message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:51:38Z" - latency: 1.050932ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:50:38Z" - latency: 935.895µs message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:49:38Z" - latency: 984.548µs message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:48:38Z" - latency: 1.0465ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:47:38Z" - latency: 1.068646ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:46:38Z" - latency: 917.906µs message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:45:38Z" - latency: 1.521994ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:44:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:25:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-120-to-network-check-target-ip-10-0-139-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-120.ec2.internal uid: cb20af25-bd09-4e1c-9ee6-c5a2c24a69b2 resourceVersion: "52775" uid: 431e607d-7ba1-41e5-ab53-c5896c6a32fc spec: sourcePod: network-check-source-685456655f-mbsl8 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-08T16:32:38Z" message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.873398ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:53:38Z" - latency: 2.394827ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:52:38Z" - latency: 2.281212ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:51:38Z" - latency: 2.190573ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:50:38Z" - latency: 2.218173ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:49:38Z" - latency: 2.185917ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:48:38Z" - latency: 2.404929ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:47:38Z" - latency: 2.823678ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:46:38Z" - latency: 1.92905ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:45:38Z" - latency: 2.117784ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:44:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:25:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-120-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-120.ec2.internal uid: cb20af25-bd09-4e1c-9ee6-c5a2c24a69b2 resourceVersion: "54479" uid: 23842be9-27bb-4c71-81ce-7c744f1820ef spec: sourcePod: network-check-source-685456655f-mbsl8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-08T16:31:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 990.762µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:55:38Z" - latency: 1.768965ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T16:55:38Z" - latency: 1.338823ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:54:38Z" - latency: 1.837294ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T16:54:38Z" - latency: 939.455µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:53:38Z" - latency: 1.945468ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T16:53:38Z" - latency: 849.366µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:52:38Z" - latency: 2.998305ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T16:52:38Z" - latency: 857.525µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:51:38Z" - latency: 2.067126ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T16:51:38Z" kind: List metadata: resourceVersion: ""