apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:31:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-67-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-67.ec2.internal uid: 74af62ec-a5e0-4a76-9cf4-94b9634b1f58 resourceVersion: "62846" uid: db8b2167-b4a3-45b2-aadf-c987c98bd27a spec: sourcePod: network-check-source-7bc5b6bf85-lvms4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T01:38:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.16208ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:13:59Z" - latency: 1.120239ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:12:59Z" - latency: 919.606µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:11:59Z" - latency: 1.412524ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:10:59Z" - latency: 887.041µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:09:59Z" - latency: 1.153052ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:08:59Z" - latency: 1.330214ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:07:59Z" - latency: 843.94µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:06:59Z" - latency: 1.113345ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:05:59Z" - latency: 1.138386ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:04:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:31:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-67-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-67.ec2.internal uid: 74af62ec-a5e0-4a76-9cf4-94b9634b1f58 resourceVersion: "62847" uid: 4330f21f-377d-4bc6-8bd9-71bbe933ef7f spec: sourcePod: network-check-source-7bc5b6bf85-lvms4 targetEndpoint: a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T01:37:59Z" message: 'load-balancer-api-external: tcp connection to a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.505431ms message: 'load-balancer-api-external: tcp connection to a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:13:59Z" - latency: 11.748519ms message: 'load-balancer-api-external: resolved host name a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:13:59Z" - latency: 4.577306ms message: 'load-balancer-api-external: tcp connection to a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:12:59Z" - latency: 8.549557ms message: 'load-balancer-api-external: resolved host name a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:12:59Z" - latency: 5.621105ms message: 'load-balancer-api-external: tcp connection to a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:11:59Z" - latency: 15.402073ms message: 'load-balancer-api-external: resolved host name a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:11:59Z" - latency: 4.162099ms message: 'load-balancer-api-external: tcp connection to a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:10:59Z" - latency: 9.483113ms message: 'load-balancer-api-external: resolved host name a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:10:59Z" - latency: 5.046398ms message: 'load-balancer-api-external: tcp connection to a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:09:59Z" - latency: 8.789298ms message: 'load-balancer-api-external: resolved host name a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:09:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:31:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-67-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-67.ec2.internal uid: 74af62ec-a5e0-4a76-9cf4-94b9634b1f58 resourceVersion: "62848" uid: e8476152-6163-4468-83b7-9e770b4e984f spec: sourcePod: network-check-source-7bc5b6bf85-lvms4 targetEndpoint: a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T01:37:59Z" message: 'load-balancer-api-internal: tcp connection to a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.586717ms message: 'load-balancer-api-internal: tcp connection to a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:13:59Z" - latency: 11.718854ms message: 'load-balancer-api-internal: resolved host name a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:13:59Z" - latency: 4.584888ms message: 'load-balancer-api-internal: tcp connection to a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:12:59Z" - latency: 8.579463ms message: 'load-balancer-api-internal: resolved host name a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:12:59Z" - latency: 5.680808ms message: 'load-balancer-api-internal: tcp connection to a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:11:59Z" - latency: 15.333427ms message: 'load-balancer-api-internal: resolved host name a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:11:59Z" - latency: 6.750152ms message: 'load-balancer-api-internal: tcp connection to a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:10:59Z" - latency: 9.279626ms message: 'load-balancer-api-internal: resolved host name a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:10:59Z" - latency: 5.116881ms message: 'load-balancer-api-internal: tcp connection to a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:09:59Z" - latency: 8.732863ms message: 'load-balancer-api-internal: resolved host name a2255fc1610704ede9dd3e2d1b104cc9-cf0588ee153d3308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:09:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:31:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-67-to-network-check-target-ip-10-0-135-67 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-67.ec2.internal uid: 74af62ec-a5e0-4a76-9cf4-94b9634b1f58 resourceVersion: "62840" uid: 9e6a3ed9-1286-4659-bb71-fc8a9e2c77e7 spec: sourcePod: network-check-source-7bc5b6bf85-lvms4 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T01:38:59Z" message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 807.22µs message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:13:59Z" - latency: 998.703µs message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:12:59Z" - latency: 846.051µs message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:11:59Z" - latency: 1.092926ms message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:10:59Z" - latency: 1.504158ms message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:09:59Z" - latency: 878.634µs message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:08:59Z" - latency: 1.541066ms message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:07:59Z" - latency: 889.965µs message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:06:59Z" - latency: 1.268001ms message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:05:59Z" - latency: 874.248µs message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:04:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:31:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-67-to-network-check-target-ip-10-0-136-148 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-67.ec2.internal uid: 74af62ec-a5e0-4a76-9cf4-94b9634b1f58 resourceVersion: "62841" uid: fd256ed0-5676-46c7-888c-4041ecda99df spec: sourcePod: network-check-source-7bc5b6bf85-lvms4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T01:38:59Z" message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.174436ms message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:13:59Z" - latency: 2.143532ms message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:12:59Z" - latency: 2.14373ms message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:11:59Z" - latency: 2.563552ms message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:10:59Z" - latency: 2.458242ms message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:09:59Z" - latency: 2.441248ms message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:08:59Z" - latency: 2.356517ms message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:07:59Z" - latency: 2.332904ms message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:06:59Z" - latency: 2.256593ms message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:05:59Z" - latency: 2.343354ms message: 'network-check-target-ip-10-0-136-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:04:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:31:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-67-to-network-check-target-ip-10-0-140-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-67.ec2.internal uid: 74af62ec-a5e0-4a76-9cf4-94b9634b1f58 resourceVersion: "62842" uid: aa0c4599-af0e-47fd-9cc5-d7f6f47865b4 spec: sourcePod: network-check-source-7bc5b6bf85-lvms4 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T01:38:59Z" message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.14814ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:13:59Z" - latency: 1.835856ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:12:59Z" - latency: 1.600245ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:11:59Z" - latency: 2.164622ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:10:59Z" - latency: 1.513394ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:09:59Z" - latency: 1.946428ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:08:59Z" - latency: 2.134817ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:07:59Z" - latency: 1.781815ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:06:59Z" - latency: 1.815517ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:05:59Z" - latency: 1.978253ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:04:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:31:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-67-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-67.ec2.internal uid: 74af62ec-a5e0-4a76-9cf4-94b9634b1f58 resourceVersion: "62845" uid: 7abef796-1d9f-4112-a5b6-35b8c98ef37e spec: sourcePod: network-check-source-7bc5b6bf85-lvms4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T01:37:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.068148ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:13:59Z" - latency: 2.089674ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:13:59Z" - latency: 1.1507ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:12:59Z" - latency: 1.93686ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:12:59Z" - latency: 916.67µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:11:59Z" - latency: 1.815005ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:11:59Z" - latency: 893.832µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:10:59Z" - latency: 2.216825ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:10:59Z" - latency: 873.432µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:09:59Z" - latency: 2.590346ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:09:59Z" kind: List metadata: resourceVersion: ""