apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:55:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-111-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-111.ec2.internal uid: c47d3136-7722-476c-b992-7112fd800537 resourceVersion: "33600" uid: 0539e439-e206-417a-92ce-1e946d998956 spec: sourcePod: network-check-source-6947749cfc-6cq7b targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-15T06:02:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.171997ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:37:08Z" - latency: 1.150322ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:36:08Z" - latency: 944.979µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:35:08Z" - latency: 1.061581ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:34:08Z" - latency: 961.137µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:33:08Z" - latency: 1.039813ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:32:08Z" - latency: 1.381744ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:31:08Z" - latency: 838.088µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:30:08Z" - latency: 891.816µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:29:08Z" - latency: 790.236µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:28:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:55:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-111-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-111.ec2.internal uid: c47d3136-7722-476c-b992-7112fd800537 resourceVersion: "33602" uid: 3023abc4-1a0a-463e-8685-72f59e8595a5 spec: sourcePod: network-check-source-6947749cfc-6cq7b targetEndpoint: a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T06:01:08Z" message: 'load-balancer-api-external: tcp connection to a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.800262ms message: 'load-balancer-api-external: tcp connection to a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:37:08Z" - latency: 6.911813ms message: 'load-balancer-api-external: resolved host name a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:37:08Z" - latency: 4.533803ms message: 'load-balancer-api-external: tcp connection to a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:36:08Z" - latency: 6.865434ms message: 'load-balancer-api-external: resolved host name a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:36:08Z" - latency: 4.265276ms message: 'load-balancer-api-external: tcp connection to a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:35:08Z" - latency: 6.573774ms message: 'load-balancer-api-external: resolved host name a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:35:08Z" - latency: 4.822568ms message: 'load-balancer-api-external: tcp connection to a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:34:08Z" - latency: 6.988153ms message: 'load-balancer-api-external: resolved host name a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:34:08Z" - latency: 5.053883ms message: 'load-balancer-api-external: tcp connection to a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:33:08Z" - latency: 5.882665ms message: 'load-balancer-api-external: resolved host name a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:33:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:55:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-111-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-111.ec2.internal uid: c47d3136-7722-476c-b992-7112fd800537 resourceVersion: "33601" uid: a88f4577-d12e-4e7b-9161-e6f44279c3f8 spec: sourcePod: network-check-source-6947749cfc-6cq7b targetEndpoint: a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T06:01:08Z" message: 'load-balancer-api-internal: tcp connection to a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.780173ms message: 'load-balancer-api-internal: tcp connection to a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:37:08Z" - latency: 6.829402ms message: 'load-balancer-api-internal: resolved host name a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:37:08Z" - latency: 4.732227ms message: 'load-balancer-api-internal: tcp connection to a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:36:08Z" - latency: 6.930712ms message: 'load-balancer-api-internal: resolved host name a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:36:08Z" - latency: 4.294719ms message: 'load-balancer-api-internal: tcp connection to a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:35:08Z" - latency: 6.556752ms message: 'load-balancer-api-internal: resolved host name a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:35:08Z" - latency: 4.832808ms message: 'load-balancer-api-internal: tcp connection to a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:34:08Z" - latency: 6.935981ms message: 'load-balancer-api-internal: resolved host name a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:34:08Z" - latency: 5.090293ms message: 'load-balancer-api-internal: tcp connection to a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:33:08Z" - latency: 5.817414ms message: 'load-balancer-api-internal: resolved host name a531d215c3ea941da8fb11f1b6ad387f-438686140d8eef34.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:33:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:55:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-111-to-network-check-target-ip-10-0-129-86 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-111.ec2.internal uid: c47d3136-7722-476c-b992-7112fd800537 resourceVersion: "33599" uid: aff112db-1f52-429e-be19-df2d3df43ed0 spec: sourcePod: network-check-source-6947749cfc-6cq7b targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-15T06:02:08Z" message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.415361ms message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:37:08Z" - latency: 2.038307ms message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:36:08Z" - latency: 2.114389ms message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:35:08Z" - latency: 2.058132ms message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:34:08Z" - latency: 2.173063ms message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:33:08Z" - latency: 2.376372ms message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:32:08Z" - latency: 2.191029ms message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:31:08Z" - latency: 2.070951ms message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:30:08Z" - latency: 2.11082ms message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:29:08Z" - latency: 2.053378ms message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:28:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:55:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-111-to-network-check-target-ip-10-0-132-4 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-111.ec2.internal uid: c47d3136-7722-476c-b992-7112fd800537 resourceVersion: "33597" uid: 89a14bd0-0c1f-41c7-afac-abcb21b39ece spec: sourcePod: network-check-source-6947749cfc-6cq7b targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-15T06:02:08Z" message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.956697ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:37:08Z" - latency: 2.24553ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:36:08Z" - latency: 1.771789ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:35:08Z" - latency: 1.876238ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:34:08Z" - latency: 1.863547ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:33:08Z" - latency: 1.902074ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:32:08Z" - latency: 1.824233ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:31:08Z" - latency: 1.870882ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:30:08Z" - latency: 2.134177ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:29:08Z" - latency: 1.883372ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:28:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:55:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-111-to-network-check-target-ip-10-0-133-111 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-111.ec2.internal uid: c47d3136-7722-476c-b992-7112fd800537 resourceVersion: "33596" uid: e088c973-a2bc-4f5a-92f9-7180078b6e52 spec: sourcePod: network-check-source-6947749cfc-6cq7b targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-15T06:02:08Z" message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 922.331µs message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:37:08Z" - latency: 784.315µs message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:36:08Z" - latency: 1.315249ms message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:35:08Z" - latency: 800.856µs message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:34:08Z" - latency: 1.012902ms message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:33:08Z" - latency: 936.429µs message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:32:08Z" - latency: 827.821µs message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:31:08Z" - latency: 1.008465ms message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:30:08Z" - latency: 882.185µs message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:29:08Z" - latency: 967.502µs message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:28:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:55:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-111-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-111.ec2.internal uid: c47d3136-7722-476c-b992-7112fd800537 resourceVersion: "33598" uid: 4f68e2cd-68dc-4022-9085-af695cad7a6c spec: sourcePod: network-check-source-6947749cfc-6cq7b targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-15T06:01:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 865.491µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:37:08Z" - latency: 1.697958ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T06:37:08Z" - latency: 955.678µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:36:08Z" - latency: 1.976587ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T06:36:08Z" - latency: 873.089µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:35:08Z" - latency: 1.751987ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T06:35:08Z" - latency: 883.313µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:34:08Z" - latency: 1.709599ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T06:34:08Z" - latency: 934.853µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:33:08Z" - latency: 1.706949ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T06:33:08Z" kind: List metadata: resourceVersion: ""