apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:29:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-47-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-47.ec2.internal uid: 3e65855c-a2be-4f8f-ae67-ccbe07245195 resourceVersion: "22049" uid: d0acd6ac-9814-48b8-afcd-c97b10c4143b spec: sourcePod: network-check-source-7bc5b6bf85-z6pz9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T17:36:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.011951ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:50:13Z" - latency: 1.512944ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:49:13Z" - latency: 1.159933ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:48:13Z" - latency: 1.547972ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:47:13Z" - latency: 1.233348ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:13Z" - latency: 1.294991ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:13Z" - latency: 1.176507ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:44:13Z" - latency: 974.223µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:43:13Z" - latency: 956.03µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:42:13Z" - latency: 970.322µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:41:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:29:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-47-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-47.ec2.internal uid: 3e65855c-a2be-4f8f-ae67-ccbe07245195 resourceVersion: "20434" uid: 7b5ac643-3ff7-4483-85d5-c7cfe03099a7 spec: sourcePod: network-check-source-7bc5b6bf85-z6pz9 targetEndpoint: afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T17:35:13Z" message: 'load-balancer-api-external: tcp connection to afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.756939ms message: 'load-balancer-api-external: tcp connection to afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:47:13Z" - latency: 7.511126ms message: 'load-balancer-api-external: resolved host name afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:47:13Z" - latency: 4.93034ms message: 'load-balancer-api-external: tcp connection to afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:13Z" - latency: 8.538412ms message: 'load-balancer-api-external: resolved host name afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:46:13Z" - latency: 5.127071ms message: 'load-balancer-api-external: tcp connection to afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:13Z" - latency: 8.565903ms message: 'load-balancer-api-external: resolved host name afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:45:13Z" - latency: 5.896468ms message: 'load-balancer-api-external: tcp connection to afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:44:13Z" - latency: 8.74923ms message: 'load-balancer-api-external: resolved host name afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:44:13Z" - latency: 4.323177ms message: 'load-balancer-api-external: tcp connection to afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:43:13Z" - latency: 8.071983ms message: 'load-balancer-api-external: resolved host name afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:43:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:29:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-47-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-47.ec2.internal uid: 3e65855c-a2be-4f8f-ae67-ccbe07245195 resourceVersion: "20435" uid: 11a3ce3f-f34f-4882-8d51-426f03d509e3 spec: sourcePod: network-check-source-7bc5b6bf85-z6pz9 targetEndpoint: afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T17:35:13Z" message: 'load-balancer-api-internal: tcp connection to afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.830079ms message: 'load-balancer-api-internal: tcp connection to afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:47:13Z" - latency: 7.566156ms message: 'load-balancer-api-internal: resolved host name afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:47:13Z" - latency: 4.951904ms message: 'load-balancer-api-internal: tcp connection to afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:13Z" - latency: 8.479042ms message: 'load-balancer-api-internal: resolved host name afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:46:13Z" - latency: 5.288676ms message: 'load-balancer-api-internal: tcp connection to afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:13Z" - latency: 8.606461ms message: 'load-balancer-api-internal: resolved host name afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:45:13Z" - latency: 4.569891ms message: 'load-balancer-api-internal: tcp connection to afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:44:13Z" - latency: 8.691489ms message: 'load-balancer-api-internal: resolved host name afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:44:13Z" - latency: 4.326544ms message: 'load-balancer-api-internal: tcp connection to afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:43:13Z" - latency: 8.032186ms message: 'load-balancer-api-internal: resolved host name afdb39d130ca94276894161df502e5d1-353d439fb0237efc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:43:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:29:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-47-to-network-check-target-ip-10-0-129-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-47.ec2.internal uid: 3e65855c-a2be-4f8f-ae67-ccbe07245195 resourceVersion: "22046" uid: 619ba02b-8039-4ef4-9e21-51f62b366be3 spec: sourcePod: network-check-source-7bc5b6bf85-z6pz9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-21T17:36:13Z" message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.463867ms message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:50:13Z" - latency: 647.618µs message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:49:13Z" - latency: 720.699µs message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:48:13Z" - latency: 795.066µs message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:47:13Z" - latency: 835.066µs message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:13Z" - latency: 1.461035ms message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:13Z" - latency: 931.585µs message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:44:13Z" - latency: 935.904µs message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:43:13Z" - latency: 865.97µs message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:42:13Z" - latency: 934.104µs message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:41:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:29:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-47-to-network-check-target-ip-10-0-136-31 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-47.ec2.internal uid: 3e65855c-a2be-4f8f-ae67-ccbe07245195 resourceVersion: "22047" uid: 9335f01e-da0d-4304-ab9f-47c548aac0ea spec: sourcePod: network-check-source-7bc5b6bf85-z6pz9 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T17:36:13Z" message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.245792ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:50:13Z" - latency: 2.37641ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:49:13Z" - latency: 2.093947ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:48:13Z" - latency: 2.146747ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:47:13Z" - latency: 2.152874ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:13Z" - latency: 2.033787ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:13Z" - latency: 2.025957ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:44:13Z" - latency: 2.281897ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:43:13Z" - latency: 2.158644ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:42:13Z" - latency: 2.223096ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:41:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:29:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-47-to-network-check-target-ip-10-0-139-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-47.ec2.internal uid: 3e65855c-a2be-4f8f-ae67-ccbe07245195 resourceVersion: "22048" uid: 0a88afa6-6624-456b-9f42-4080fc407837 spec: sourcePod: network-check-source-7bc5b6bf85-z6pz9 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T17:36:13Z" message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.90118ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:50:13Z" - latency: 1.908763ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:49:13Z" - latency: 1.624126ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:48:13Z" - latency: 1.691888ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:47:13Z" - latency: 1.600316ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:13Z" - latency: 2.086829ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:13Z" - latency: 1.767786ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:44:13Z" - latency: 1.842555ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:43:13Z" - latency: 1.577919ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:42:13Z" - latency: 1.670198ms message: 'network-check-target-ip-10-0-139-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:41:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:29:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-47-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-47.ec2.internal uid: 3e65855c-a2be-4f8f-ae67-ccbe07245195 resourceVersion: "20433" uid: a9a93ce0-180f-474e-9536-e581f2f70ae3 spec: sourcePod: network-check-source-7bc5b6bf85-z6pz9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T17:35:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 889.429µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:47:13Z" - latency: 1.762609ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:47:13Z" - latency: 785.2µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:13Z" - latency: 1.637102ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:46:13Z" - latency: 923.001µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:13Z" - latency: 2.065527ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:45:13Z" - latency: 696.722µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:44:13Z" - latency: 2.044126ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:44:13Z" - latency: 662.78µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:43:13Z" - latency: 1.903765ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:43:13Z" kind: List metadata: resourceVersion: ""