apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T06:39:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: bea1eeb0-9f5a-4142-8efc-3ce93790a121 resourceVersion: "19600" uid: 56c966b2-d573-48c3-98a8-f9e144191aa9 spec: sourcePod: network-check-source-685456655f-t7v7d targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-08T06:46:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 976.331µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:00:33Z" - latency: 1.320796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:59:33Z" - latency: 954.892µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:58:33Z" - latency: 978.779µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:57:33Z" - latency: 1.015621ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:56:33Z" - latency: 1.03924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:55:33Z" - latency: 1.016088ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:54:33Z" - latency: 1.0508ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:53:33Z" - latency: 1.19709ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:52:33Z" - latency: 1.046635ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:51:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T06:39:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: bea1eeb0-9f5a-4142-8efc-3ce93790a121 resourceVersion: "20869" uid: ff8551d6-8335-48ab-9783-8de57e53117c spec: sourcePod: network-check-source-685456655f-t7v7d targetEndpoint: aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T06:45:33Z" message: 'load-balancer-api-external: tcp connection to aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.522549ms message: 'load-balancer-api-external: tcp connection to aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:03:33Z" - latency: 7.643105ms message: 'load-balancer-api-external: resolved host name aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T07:03:33Z" - latency: 3.987354ms message: 'load-balancer-api-external: tcp connection to aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:02:33Z" - latency: 11.153532ms message: 'load-balancer-api-external: resolved host name aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T07:02:33Z" - latency: 5.286863ms message: 'load-balancer-api-external: tcp connection to aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:01:33Z" - latency: 8.960093ms message: 'load-balancer-api-external: resolved host name aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T07:01:33Z" - latency: 5.176477ms message: 'load-balancer-api-external: tcp connection to aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:00:33Z" - latency: 8.492345ms message: 'load-balancer-api-external: resolved host name aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T07:00:33Z" - latency: 3.844492ms message: 'load-balancer-api-external: tcp connection to aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:59:33Z" - latency: 7.777595ms message: 'load-balancer-api-external: resolved host name aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T06:59:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T06:39:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: bea1eeb0-9f5a-4142-8efc-3ce93790a121 resourceVersion: "20868" uid: 757ad2cb-0541-4747-a755-b1cb1a7355a8 spec: sourcePod: network-check-source-685456655f-t7v7d targetEndpoint: aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T06:45:33Z" message: 'load-balancer-api-internal: tcp connection to aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.091405ms message: 'load-balancer-api-internal: tcp connection to aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:03:33Z" - latency: 7.600664ms message: 'load-balancer-api-internal: resolved host name aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T07:03:33Z" - latency: 3.829215ms message: 'load-balancer-api-internal: tcp connection to aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:02:33Z" - latency: 11.216332ms message: 'load-balancer-api-internal: resolved host name aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T07:02:33Z" - latency: 5.299817ms message: 'load-balancer-api-internal: tcp connection to aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:01:33Z" - latency: 9.028996ms message: 'load-balancer-api-internal: resolved host name aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T07:01:33Z" - latency: 5.207793ms message: 'load-balancer-api-internal: tcp connection to aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:00:33Z" - latency: 8.618402ms message: 'load-balancer-api-internal: resolved host name aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T07:00:33Z" - latency: 3.791468ms message: 'load-balancer-api-internal: tcp connection to aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:59:33Z" - latency: 7.722343ms message: 'load-balancer-api-internal: resolved host name aa6551684b4554e00be23ef4ce0e6432-0c10fd5d2f9d43b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T06:59:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T06:39:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-network-check-target-ip-10-0-132-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: bea1eeb0-9f5a-4142-8efc-3ce93790a121 resourceVersion: "19597" uid: 2b33570d-1ad3-4ac7-95d8-1116bac92ff6 spec: sourcePod: network-check-source-685456655f-t7v7d targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-08T06:46:33Z" message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 831.457µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:00:33Z" - latency: 1.459134ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:59:33Z" - latency: 1.468361ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:58:33Z" - latency: 899.513µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:57:33Z" - latency: 956.614µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:56:33Z" - latency: 758.507µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:55:33Z" - latency: 1.157844ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:54:33Z" - latency: 833.519µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:53:33Z" - latency: 1.382056ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:52:33Z" - latency: 1.172683ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:51:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T06:39:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-network-check-target-ip-10-0-132-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: bea1eeb0-9f5a-4142-8efc-3ce93790a121 resourceVersion: "19599" uid: 51a5e5f9-7f10-4953-9c96-ca8ff0a02d70 spec: sourcePod: network-check-source-685456655f-t7v7d targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-08T06:46:33Z" message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.233445ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:00:33Z" - latency: 2.282562ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:59:33Z" - latency: 2.891259ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:58:33Z" - latency: 2.4053ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:57:33Z" - latency: 2.428685ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:56:33Z" - latency: 2.339929ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:55:33Z" - latency: 2.275662ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:54:33Z" - latency: 2.784052ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:53:33Z" - latency: 2.474061ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:52:33Z" - latency: 2.335646ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:51:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T06:39:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-network-check-target-ip-10-0-135-120 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: bea1eeb0-9f5a-4142-8efc-3ce93790a121 resourceVersion: "19598" uid: 80fdce7f-47f2-4db6-b409-8155e35fe27a spec: sourcePod: network-check-source-685456655f-t7v7d targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-08T06:46:33Z" message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.183271ms message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:00:33Z" - latency: 2.577616ms message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:59:33Z" - latency: 2.299613ms message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:58:33Z" - latency: 2.083851ms message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:57:33Z" - latency: 2.319879ms message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:56:33Z" - latency: 2.152055ms message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:55:33Z" - latency: 2.087457ms message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:54:33Z" - latency: 2.300582ms message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:53:33Z" - latency: 2.484171ms message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:52:33Z" - latency: 2.307544ms message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:51:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T06:39:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: bea1eeb0-9f5a-4142-8efc-3ce93790a121 resourceVersion: "20867" uid: 33bc908c-dbd0-4595-bbba-658860b62fe2 spec: sourcePod: network-check-source-685456655f-t7v7d targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-08T06:45:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 848.215µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:03:33Z" - latency: 1.573497ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T07:03:33Z" - latency: 977.048µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:02:33Z" - latency: 1.828209ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T07:02:33Z" - latency: 1.004482ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:01:33Z" - latency: 1.816819ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T07:01:33Z" - latency: 850.633µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T07:00:33Z" - latency: 2.182482ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T07:00:33Z" - latency: 917.501µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T06:59:33Z" - latency: 1.744099ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T06:59:33Z" kind: List metadata: resourceVersion: ""