apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:11:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-184-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-184.ec2.internal uid: da03a20c-3c32-4ffd-921d-95ff138cab2e resourceVersion: "54680" uid: 2b505f9e-d02f-4f6a-a272-77ff4c260f5a spec: sourcePod: network-check-source-869dcfcdcd-pxj8g targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T17:18:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.319243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:46:53Z" - latency: 1.043246ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:45:53Z" - latency: 1.270478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:44:53Z" - latency: 847.877µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:43:53Z" - latency: 1.061867ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:42:53Z" - latency: 1.148163ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:41:53Z" - latency: 1.288046ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:40:53Z" - latency: 962.207µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:39:53Z" - latency: 1.397789ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:38:53Z" - latency: 996.149µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:37:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:11:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-184-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-184.ec2.internal uid: da03a20c-3c32-4ffd-921d-95ff138cab2e resourceVersion: "55713" uid: 2d108ce1-5389-4458-9541-b50ad8960bb1 spec: sourcePod: network-check-source-869dcfcdcd-pxj8g targetEndpoint: a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T17:17:53Z" message: 'load-balancer-api-external: tcp connection to a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.75976ms message: 'load-balancer-api-external: tcp connection to a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:47:53Z" - latency: 8.635798ms message: 'load-balancer-api-external: resolved host name a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:47:53Z" - latency: 13.778498ms message: 'load-balancer-api-external: tcp connection to a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:46:53Z" - latency: 7.012567ms message: 'load-balancer-api-external: resolved host name a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:46:53Z" - latency: 4.48222ms message: 'load-balancer-api-external: tcp connection to a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:45:53Z" - latency: 7.138618ms message: 'load-balancer-api-external: resolved host name a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:45:53Z" - latency: 3.773174ms message: 'load-balancer-api-external: tcp connection to a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:44:53Z" - latency: 9.413302ms message: 'load-balancer-api-external: resolved host name a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:44:53Z" - latency: 5.410177ms message: 'load-balancer-api-external: tcp connection to a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:43:53Z" - latency: 7.954919ms message: 'load-balancer-api-external: resolved host name a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:43:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:11:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-184-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-184.ec2.internal uid: da03a20c-3c32-4ffd-921d-95ff138cab2e resourceVersion: "55712" uid: 893c9613-0233-4593-aaf1-ebd8ac1ac179 spec: sourcePod: network-check-source-869dcfcdcd-pxj8g targetEndpoint: a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T17:17:53Z" message: 'load-balancer-api-internal: tcp connection to a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.382237ms message: 'load-balancer-api-internal: tcp connection to a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:47:53Z" - latency: 8.579669ms message: 'load-balancer-api-internal: resolved host name a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:47:53Z" - latency: 5.925153ms message: 'load-balancer-api-internal: tcp connection to a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:46:53Z" - latency: 6.929615ms message: 'load-balancer-api-internal: resolved host name a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:46:53Z" - latency: 4.16839ms message: 'load-balancer-api-internal: tcp connection to a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:45:53Z" - latency: 7.120226ms message: 'load-balancer-api-internal: resolved host name a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:45:53Z" - latency: 4.692488ms message: 'load-balancer-api-internal: tcp connection to a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:44:53Z" - latency: 9.366604ms message: 'load-balancer-api-internal: resolved host name a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:44:53Z" - latency: 5.3991ms message: 'load-balancer-api-internal: tcp connection to a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:43:53Z" - latency: 7.929232ms message: 'load-balancer-api-internal: resolved host name a9a5e9ce5686d4561a422dc991910eeb-953f4040a0d4076e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:43:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:11:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-184-to-network-check-target-ip-10-0-133-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-184.ec2.internal uid: da03a20c-3c32-4ffd-921d-95ff138cab2e resourceVersion: "54679" uid: 7b2616e6-a40c-4313-90d2-c0bc95d37e02 spec: sourcePod: network-check-source-869dcfcdcd-pxj8g targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T17:18:53Z" message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.599031ms message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:46:53Z" - latency: 2.153129ms message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:45:53Z" - latency: 2.433438ms message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:44:53Z" - latency: 2.113645ms message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:43:53Z" - latency: 2.499586ms message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:42:53Z" - latency: 2.342828ms message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:41:53Z" - latency: 2.195604ms message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:40:53Z" - latency: 2.565475ms message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:39:53Z" - latency: 2.414507ms message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:38:53Z" - latency: 2.08858ms message: 'network-check-target-ip-10-0-133-241: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:37:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:11:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-184-to-network-check-target-ip-10-0-135-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-184.ec2.internal uid: da03a20c-3c32-4ffd-921d-95ff138cab2e resourceVersion: "54682" uid: 9a813507-494c-486b-bd56-3a334799db84 spec: sourcePod: network-check-source-869dcfcdcd-pxj8g targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T17:18:53Z" message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 965.116µs message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:46:53Z" - latency: 959.745µs message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:45:53Z" - latency: 855.305µs message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:44:53Z" - latency: 1.375526ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:43:53Z" - latency: 1.204806ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:42:53Z" - latency: 1.170222ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:41:53Z" - latency: 1.470247ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:40:53Z" - latency: 1.542054ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:39:53Z" - latency: 955.736µs message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:38:53Z" - latency: 971.179µs message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:37:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:11:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-184-to-network-check-target-ip-10-0-135-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-184.ec2.internal uid: da03a20c-3c32-4ffd-921d-95ff138cab2e resourceVersion: "54681" uid: 236459c7-2f47-4ac8-ada2-81cdc7c8717a spec: sourcePod: network-check-source-869dcfcdcd-pxj8g targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T17:18:53Z" message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.178898ms message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:46:53Z" - latency: 1.58733ms message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:45:53Z" - latency: 2.089987ms message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:44:53Z" - latency: 1.850233ms message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:43:53Z" - latency: 2.131555ms message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:42:53Z" - latency: 1.935713ms message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:41:53Z" - latency: 1.887824ms message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:40:53Z" - latency: 2.024001ms message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:39:53Z" - latency: 1.638476ms message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:38:53Z" - latency: 1.991523ms message: 'network-check-target-ip-10-0-135-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:37:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:11:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-184-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-184.ec2.internal uid: da03a20c-3c32-4ffd-921d-95ff138cab2e resourceVersion: "55711" uid: a7eead2d-4af0-4e56-aefb-707d3d8b04dc spec: sourcePod: network-check-source-869dcfcdcd-pxj8g targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T17:17:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 903.741µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:47:53Z" - latency: 1.69882ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:47:53Z" - latency: 866.584µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:46:53Z" - latency: 1.93489ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:46:53Z" - latency: 1.254105ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:45:53Z" - latency: 1.783426ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:45:53Z" - latency: 1.106382ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:44:53Z" - latency: 1.685154ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:44:53Z" - latency: 813.734µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:43:53Z" - latency: 1.922088ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:43:53Z" kind: List metadata: resourceVersion: ""