apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:44:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-170-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-170.ec2.internal uid: d823a87a-9d47-43d0-a8e2-58d3e7ff1389 resourceVersion: "31988" uid: af7c821a-24b0-46b8-9208-23757ff266cc spec: sourcePod: network-check-source-869dcfcdcd-4jxqd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T18:51:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.357685ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:26:01Z" - latency: 988.245µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:25:01Z" - latency: 1.462546ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:24:01Z" - latency: 1.431626ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:23:01Z" - latency: 1.130982ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:01Z" - latency: 1.484089ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:01Z" - latency: 1.208204ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:01Z" - latency: 874.4µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:01Z" - latency: 1.131315ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:01Z" - latency: 918.68µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:44:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-170-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-170.ec2.internal uid: d823a87a-9d47-43d0-a8e2-58d3e7ff1389 resourceVersion: "31990" uid: 538ef0ea-b0b2-4701-a966-5f452f679afd spec: sourcePod: network-check-source-869dcfcdcd-4jxqd targetEndpoint: a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T18:50:01Z" message: 'load-balancer-api-external: tcp connection to a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.399343ms message: 'load-balancer-api-external: tcp connection to a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:26:01Z" - latency: 8.831401ms message: 'load-balancer-api-external: resolved host name a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:26:01Z" - latency: 5.362528ms message: 'load-balancer-api-external: tcp connection to a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:25:01Z" - latency: 9.299132ms message: 'load-balancer-api-external: resolved host name a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:25:01Z" - latency: 5.115266ms message: 'load-balancer-api-external: tcp connection to a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:24:01Z" - latency: 11.424496ms message: 'load-balancer-api-external: resolved host name a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:24:01Z" - latency: 7.657357ms message: 'load-balancer-api-external: tcp connection to a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:23:01Z" - latency: 9.835157ms message: 'load-balancer-api-external: resolved host name a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:23:01Z" - latency: 5.750779ms message: 'load-balancer-api-external: tcp connection to a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:01Z" - latency: 8.779748ms message: 'load-balancer-api-external: resolved host name a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:22:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:44:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-170-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-170.ec2.internal uid: d823a87a-9d47-43d0-a8e2-58d3e7ff1389 resourceVersion: "31989" uid: 2975a10b-300c-4ecf-a207-68b3d67c32d5 spec: sourcePod: network-check-source-869dcfcdcd-4jxqd targetEndpoint: a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T18:50:01Z" message: 'load-balancer-api-internal: tcp connection to a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.382336ms message: 'load-balancer-api-internal: tcp connection to a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:26:01Z" - latency: 8.739763ms message: 'load-balancer-api-internal: resolved host name a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:26:01Z" - latency: 5.424681ms message: 'load-balancer-api-internal: tcp connection to a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:25:01Z" - latency: 9.337437ms message: 'load-balancer-api-internal: resolved host name a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:25:01Z" - latency: 5.163134ms message: 'load-balancer-api-internal: tcp connection to a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:24:01Z" - latency: 11.340238ms message: 'load-balancer-api-internal: resolved host name a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:24:01Z" - latency: 5.938998ms message: 'load-balancer-api-internal: tcp connection to a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:23:01Z" - latency: 9.796457ms message: 'load-balancer-api-internal: resolved host name a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:23:01Z" - latency: 5.826074ms message: 'load-balancer-api-internal: tcp connection to a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:01Z" - latency: 8.728465ms message: 'load-balancer-api-internal: resolved host name a818c22d8a9944ee4a809940d34c2675-cf7193507ec9b9ea.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:22:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:44:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-170-to-network-check-target-ip-10-0-129-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-170.ec2.internal uid: d823a87a-9d47-43d0-a8e2-58d3e7ff1389 resourceVersion: "31984" uid: cee8e1b3-6615-42c2-be56-0d180f5f7ea4 spec: sourcePod: network-check-source-869dcfcdcd-4jxqd targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T18:51:01Z" message: 'network-check-target-ip-10-0-129-73: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.904883ms message: 'network-check-target-ip-10-0-129-73: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:26:01Z" - latency: 2.197258ms message: 'network-check-target-ip-10-0-129-73: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:25:01Z" - latency: 1.804006ms message: 'network-check-target-ip-10-0-129-73: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:24:01Z" - latency: 1.820153ms message: 'network-check-target-ip-10-0-129-73: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:23:01Z" - latency: 1.825324ms message: 'network-check-target-ip-10-0-129-73: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:01Z" - latency: 1.939188ms message: 'network-check-target-ip-10-0-129-73: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:01Z" - latency: 2.005134ms message: 'network-check-target-ip-10-0-129-73: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:01Z" - latency: 1.876873ms message: 'network-check-target-ip-10-0-129-73: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:01Z" - latency: 1.946131ms message: 'network-check-target-ip-10-0-129-73: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:01Z" - latency: 1.771331ms message: 'network-check-target-ip-10-0-129-73: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:44:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-170-to-network-check-target-ip-10-0-138-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-170.ec2.internal uid: d823a87a-9d47-43d0-a8e2-58d3e7ff1389 resourceVersion: "31985" uid: 8b22b8f9-e83d-4796-8d5f-d766fdb0de08 spec: sourcePod: network-check-source-869dcfcdcd-4jxqd targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T18:51:01Z" message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.283298ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:26:01Z" - latency: 2.289516ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:25:01Z" - latency: 2.103469ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:24:01Z" - latency: 2.112754ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:23:01Z" - latency: 2.393023ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:01Z" - latency: 2.14896ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:01Z" - latency: 2.383073ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:01Z" - latency: 2.358075ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:01Z" - latency: 2.448214ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:01Z" - latency: 3.268066ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:44:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-170-to-network-check-target-ip-10-0-142-170 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-170.ec2.internal uid: d823a87a-9d47-43d0-a8e2-58d3e7ff1389 resourceVersion: "31986" uid: bb50c05e-f4dc-440d-b885-cd62a0296091 spec: sourcePod: network-check-source-869dcfcdcd-4jxqd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T18:51:01Z" message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.486469ms message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:26:01Z" - latency: 1.521037ms message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:25:01Z" - latency: 878.04µs message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:24:01Z" - latency: 757.476µs message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:23:01Z" - latency: 1.262735ms message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:01Z" - latency: 887.779µs message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:21:01Z" - latency: 800.065µs message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:20:01Z" - latency: 765.094µs message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:19:01Z" - latency: 888.025µs message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:18:01Z" - latency: 1.019063ms message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:17:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:44:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-170-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-170.ec2.internal uid: d823a87a-9d47-43d0-a8e2-58d3e7ff1389 resourceVersion: "31987" uid: 34680cdf-4084-4555-aa99-fb4526769b11 spec: sourcePod: network-check-source-869dcfcdcd-4jxqd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T18:50:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.303232ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:26:01Z" - latency: 1.547016ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:26:01Z" - latency: 1.096064ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:25:01Z" - latency: 1.946074ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:25:01Z" - latency: 684.57µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:24:01Z" - latency: 1.706459ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:24:01Z" - latency: 1.010043ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:23:01Z" - latency: 1.670146ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:23:01Z" - latency: 849.84µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:22:01Z" - latency: 2.065425ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:22:01Z" kind: List metadata: resourceVersion: ""