apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T16:10:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.ec2.internal uid: 97b34cf0-68bf-40bf-b0ea-1d5c8f966ab3 resourceVersion: "65023" uid: 35cf17f9-3a60-4998-ba11-206f218e858f spec: sourcePod: network-check-source-7d88cb55d8-m8cfd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T16:17:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 917.868µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:52:51Z" - latency: 905.392µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:51:51Z" - latency: 1.098645ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:50:51Z" - latency: 1.273249ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:49:51Z" - latency: 1.026971ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:48:51Z" - latency: 1.056029ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:47:51Z" - latency: 2.892793ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:46:51Z" - latency: 898.872µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:45:51Z" - latency: 1.512873ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:44:51Z" - latency: 1.400573ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:43:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T16:10:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.ec2.internal uid: 97b34cf0-68bf-40bf-b0ea-1d5c8f966ab3 resourceVersion: "65024" uid: 6d28905a-578b-43e9-8b7d-76ed1e722c9a spec: sourcePod: network-check-source-7d88cb55d8-m8cfd targetEndpoint: a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T16:16:51Z" message: 'load-balancer-api-external: tcp connection to a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.178733ms message: 'load-balancer-api-external: tcp connection to a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:52:51Z" - latency: 7.535178ms message: 'load-balancer-api-external: resolved host name a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:52:51Z" - latency: 5.206102ms message: 'load-balancer-api-external: tcp connection to a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:51:51Z" - latency: 7.529446ms message: 'load-balancer-api-external: resolved host name a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:51:51Z" - latency: 4.866612ms message: 'load-balancer-api-external: tcp connection to a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:50:51Z" - latency: 8.036272ms message: 'load-balancer-api-external: resolved host name a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:50:51Z" - latency: 4.749465ms message: 'load-balancer-api-external: tcp connection to a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:49:51Z" - latency: 6.576218ms message: 'load-balancer-api-external: resolved host name a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:49:51Z" - latency: 4.892533ms message: 'load-balancer-api-external: tcp connection to a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:48:51Z" - latency: 13.474646ms message: 'load-balancer-api-external: resolved host name a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:48:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T16:10:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.ec2.internal uid: 97b34cf0-68bf-40bf-b0ea-1d5c8f966ab3 resourceVersion: "65025" uid: ff0cd2c2-ea8b-407b-8bdf-476f54423369 spec: sourcePod: network-check-source-7d88cb55d8-m8cfd targetEndpoint: a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T16:16:51Z" message: 'load-balancer-api-internal: tcp connection to a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.368499ms message: 'load-balancer-api-internal: tcp connection to a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:52:51Z" - latency: 7.355695ms message: 'load-balancer-api-internal: resolved host name a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:52:51Z" - latency: 3.935122ms message: 'load-balancer-api-internal: tcp connection to a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:51:51Z" - latency: 7.464863ms message: 'load-balancer-api-internal: resolved host name a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:51:51Z" - latency: 4.363285ms message: 'load-balancer-api-internal: tcp connection to a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:50:51Z" - latency: 7.910567ms message: 'load-balancer-api-internal: resolved host name a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:50:51Z" - latency: 4.807402ms message: 'load-balancer-api-internal: tcp connection to a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:49:51Z" - latency: 6.52958ms message: 'load-balancer-api-internal: resolved host name a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:49:51Z" - latency: 4.934793ms message: 'load-balancer-api-internal: tcp connection to a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:48:51Z" - latency: 13.289609ms message: 'load-balancer-api-internal: resolved host name a546153fc94c04011a0871d6008cb4ce-6310bfb4f0a3a4e2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:48:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T16:10:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-network-check-target-ip-10-0-130-189 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.ec2.internal uid: 97b34cf0-68bf-40bf-b0ea-1d5c8f966ab3 resourceVersion: "65018" uid: 42335397-b9b1-4240-bee8-473a7415d7db spec: sourcePod: network-check-source-7d88cb55d8-m8cfd targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T16:17:51Z" message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.254629ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:52:51Z" - latency: 1.41937ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:51:51Z" - latency: 985.394µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:50:51Z" - latency: 1.055802ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:49:51Z" - latency: 1.046759ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:48:51Z" - latency: 936.299µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:47:51Z" - latency: 3.324375ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:46:51Z" - latency: 1.315544ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:45:51Z" - latency: 1.098229ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:44:51Z" - latency: 974.861µs message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:43:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T16:10:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-network-check-target-ip-10-0-134-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.ec2.internal uid: 97b34cf0-68bf-40bf-b0ea-1d5c8f966ab3 resourceVersion: "65019" uid: 72ff3ac3-9322-45bf-b65b-e7653da01eeb spec: sourcePod: network-check-source-7d88cb55d8-m8cfd targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T16:17:51Z" message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.307941ms message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:52:51Z" - latency: 2.236876ms message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:51:51Z" - latency: 2.593255ms message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:50:51Z" - latency: 2.224038ms message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:49:51Z" - latency: 2.396996ms message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:48:51Z" - latency: 2.396765ms message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:47:51Z" - latency: 3.473409ms message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:46:51Z" - latency: 2.254728ms message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:45:51Z" - latency: 2.291091ms message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:44:51Z" - latency: 2.892606ms message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:43:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T16:10:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-network-check-target-ip-10-0-134-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.ec2.internal uid: 97b34cf0-68bf-40bf-b0ea-1d5c8f966ab3 resourceVersion: "65020" uid: 7ef6c4b1-c5b4-4337-8c31-c9de67a7fd0f spec: sourcePod: network-check-source-7d88cb55d8-m8cfd targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T16:17:51Z" message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.489581ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:52:51Z" - latency: 2.326322ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:51:51Z" - latency: 2.347909ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:50:51Z" - latency: 2.3283ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:49:51Z" - latency: 2.264554ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:48:51Z" - latency: 2.344893ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:47:51Z" - latency: 3.397725ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:46:51Z" - latency: 2.389936ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:45:51Z" - latency: 2.221752ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:44:51Z" - latency: 2.392773ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:43:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T16:10:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-189-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-189.ec2.internal uid: 97b34cf0-68bf-40bf-b0ea-1d5c8f966ab3 resourceVersion: "65021" uid: 2ce62131-3921-4c3a-bb9c-60b266f49f06 spec: sourcePod: network-check-source-7d88cb55d8-m8cfd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T16:16:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.226406ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:52:51Z" - latency: 2.372458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T16:52:51Z" - latency: 1.238477ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:51:51Z" - latency: 2.001298ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T16:51:51Z" - latency: 1.095892ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:50:51Z" - latency: 1.702533ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T16:50:51Z" - latency: 1.291534ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:49:51Z" - latency: 1.607022ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T16:49:51Z" - latency: 1.05468ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:48:51Z" - latency: 2.220327ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T16:48:51Z" kind: List metadata: resourceVersion: ""