apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T21:20:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-61-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-61.ec2.internal uid: fd683307-f3d8-423e-9d8f-5c29cff0dff7 resourceVersion: "68350" uid: d8c43595-e333-47fa-9afc-07e1b019e55e spec: sourcePod: network-check-source-6f8b768455-7vlzv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-15T21:27:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 948.639µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:55:19Z" - latency: 1.081248ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:54:19Z" - latency: 1.053117ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:53:19Z" - latency: 1.110834ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:52:19Z" - latency: 896.868µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:51:19Z" - latency: 913.265µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:50:19Z" - latency: 964.349µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:49:19Z" - latency: 939.942µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:48:19Z" - latency: 1.038527ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:47:19Z" - latency: 1.333778ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:46:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T21:20:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-61-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-61.ec2.internal uid: fd683307-f3d8-423e-9d8f-5c29cff0dff7 resourceVersion: "69348" uid: 0508457b-aeb6-4d51-925c-d5d0247a6e39 spec: sourcePod: network-check-source-6f8b768455-7vlzv targetEndpoint: ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T21:26:19Z" message: 'load-balancer-api-external: tcp connection to ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.149923ms message: 'load-balancer-api-external: tcp connection to ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:56:19Z" - latency: 10.643544ms message: 'load-balancer-api-external: resolved host name ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:56:19Z" - latency: 4.98379ms message: 'load-balancer-api-external: tcp connection to ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:55:19Z" - latency: 12.937724ms message: 'load-balancer-api-external: resolved host name ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:55:19Z" - latency: 4.703236ms message: 'load-balancer-api-external: tcp connection to ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:54:19Z" - latency: 10.825728ms message: 'load-balancer-api-external: resolved host name ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:54:19Z" - latency: 3.252089ms message: 'load-balancer-api-external: tcp connection to ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:53:19Z" - latency: 8.994381ms message: 'load-balancer-api-external: resolved host name ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:53:19Z" - latency: 4.783751ms message: 'load-balancer-api-external: tcp connection to ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:52:19Z" - latency: 11.413189ms message: 'load-balancer-api-external: resolved host name ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:52:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T21:20:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-61-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-61.ec2.internal uid: fd683307-f3d8-423e-9d8f-5c29cff0dff7 resourceVersion: "69349" uid: 708a9570-209d-4435-acf4-3c512ec92025 spec: sourcePod: network-check-source-6f8b768455-7vlzv targetEndpoint: ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T21:26:19Z" message: 'load-balancer-api-internal: tcp connection to ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.168464ms message: 'load-balancer-api-internal: tcp connection to ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:56:19Z" - latency: 10.676284ms message: 'load-balancer-api-internal: resolved host name ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:56:19Z" - latency: 5.208787ms message: 'load-balancer-api-internal: tcp connection to ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:55:19Z" - latency: 12.962022ms message: 'load-balancer-api-internal: resolved host name ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:55:19Z" - latency: 4.174615ms message: 'load-balancer-api-internal: tcp connection to ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:54:19Z" - latency: 10.856749ms message: 'load-balancer-api-internal: resolved host name ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:54:19Z" - latency: 3.25817ms message: 'load-balancer-api-internal: tcp connection to ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:53:19Z" - latency: 9.014853ms message: 'load-balancer-api-internal: resolved host name ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:53:19Z" - latency: 4.798052ms message: 'load-balancer-api-internal: tcp connection to ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:52:19Z" - latency: 11.45343ms message: 'load-balancer-api-internal: resolved host name ab8b2939b77fa4165aa5cafee514cf17-5f5fcf57f65d24b2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T21:52:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T21:20:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-61-to-network-check-target-ip-10-0-129-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-61.ec2.internal uid: fd683307-f3d8-423e-9d8f-5c29cff0dff7 resourceVersion: "68348" uid: 9d1c38de-e078-45bd-b341-a70c78adbf66 spec: sourcePod: network-check-source-6f8b768455-7vlzv targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-15T21:27:19Z" message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.344049ms message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:55:19Z" - latency: 2.316796ms message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:54:19Z" - latency: 2.195445ms message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:53:19Z" - latency: 2.522162ms message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:52:19Z" - latency: 2.29024ms message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:51:19Z" - latency: 2.09563ms message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:50:19Z" - latency: 2.60014ms message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:49:19Z" - latency: 2.675192ms message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:48:19Z" - latency: 2.524728ms message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:47:19Z" - latency: 2.076579ms message: 'network-check-target-ip-10-0-129-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:46:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T21:20:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-61-to-network-check-target-ip-10-0-133-61 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-61.ec2.internal uid: fd683307-f3d8-423e-9d8f-5c29cff0dff7 resourceVersion: "68347" uid: d2a4398d-79ac-4c67-a715-492d0d913e44 spec: sourcePod: network-check-source-6f8b768455-7vlzv targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-15T21:27:19Z" message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 884.913µs message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:55:19Z" - latency: 1.074881ms message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:54:19Z" - latency: 976.791µs message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:53:19Z" - latency: 1.444854ms message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:52:19Z" - latency: 1.351185ms message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:51:19Z" - latency: 838.63µs message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:50:19Z" - latency: 996.658µs message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:49:19Z" - latency: 1.390014ms message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:48:19Z" - latency: 1.153483ms message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:47:19Z" - latency: 1.095201ms message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:46:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T21:20:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-61-to-network-check-target-ip-10-0-135-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-61.ec2.internal uid: fd683307-f3d8-423e-9d8f-5c29cff0dff7 resourceVersion: "68349" uid: eb30dd16-c9d5-4017-b75d-e91c9dfa6835 spec: sourcePod: network-check-source-6f8b768455-7vlzv targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-15T21:27:19Z" message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.393924ms message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:55:19Z" - latency: 2.691984ms message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:54:19Z" - latency: 2.520629ms message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:53:19Z" - latency: 2.49098ms message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:52:19Z" - latency: 2.468856ms message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:51:19Z" - latency: 2.481588ms message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:50:19Z" - latency: 2.693509ms message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:49:19Z" - latency: 2.582241ms message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:48:19Z" - latency: 2.616407ms message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:47:19Z" - latency: 2.496282ms message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:46:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T21:20:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-61-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-61.ec2.internal uid: fd683307-f3d8-423e-9d8f-5c29cff0dff7 resourceVersion: "69347" uid: 20aa688b-35a1-4e2f-ba04-ca6c4de37d7f spec: sourcePod: network-check-source-6f8b768455-7vlzv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-15T21:26:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.072532ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:56:19Z" - latency: 2.090145ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T21:56:19Z" - latency: 906.218µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:55:19Z" - latency: 1.792374ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T21:55:19Z" - latency: 859.162µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:54:19Z" - latency: 2.027785ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T21:54:19Z" - latency: 973.563µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:53:19Z" - latency: 2.11758ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T21:53:19Z" - latency: 1.156225ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T21:52:19Z" - latency: 1.812872ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T21:52:19Z" kind: List metadata: resourceVersion: ""