apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:02:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-251-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-251.ec2.internal uid: 641222cf-9fd5-4a21-a0ed-7d7783cf7f51 resourceVersion: "32433" uid: 127cc6a8-1dde-4744-8eed-89e33dad5f4c spec: sourcePod: network-check-source-869dcfcdcd-w4tzb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T19:09:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 768.21µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:41Z" - latency: 822.193µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:41Z" - latency: 1.344809ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:41Z" - latency: 1.338362ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:41Z" - latency: 925.39µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:41Z" - latency: 774.709µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:39:41Z" - latency: 1.004921ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:38:41Z" - latency: 988.739µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:37:41Z" - latency: 856.179µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:36:41Z" - latency: 792.447µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:35:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:02:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-251-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-251.ec2.internal uid: 641222cf-9fd5-4a21-a0ed-7d7783cf7f51 resourceVersion: "32434" uid: 3734f39f-1df4-4397-bcf0-3e94c1801a22 spec: sourcePod: network-check-source-869dcfcdcd-w4tzb targetEndpoint: a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T19:08:41Z" message: 'load-balancer-api-external: tcp connection to a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.142076ms message: 'load-balancer-api-external: tcp connection to a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:41Z" - latency: 8.910001ms message: 'load-balancer-api-external: resolved host name a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:44:41Z" - latency: 4.249427ms message: 'load-balancer-api-external: tcp connection to a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:41Z" - latency: 6.732951ms message: 'load-balancer-api-external: resolved host name a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:43:41Z" - latency: 4.410846ms message: 'load-balancer-api-external: tcp connection to a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:41Z" - latency: 8.835562ms message: 'load-balancer-api-external: resolved host name a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:42:41Z" - latency: 5.212973ms message: 'load-balancer-api-external: tcp connection to a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:41Z" - latency: 6.39938ms message: 'load-balancer-api-external: resolved host name a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:41:41Z" - latency: 6.627005ms message: 'load-balancer-api-external: tcp connection to a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:41Z" - latency: 8.271851ms message: 'load-balancer-api-external: resolved host name a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:40:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:02:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-251-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-251.ec2.internal uid: 641222cf-9fd5-4a21-a0ed-7d7783cf7f51 resourceVersion: "32435" uid: befa1bd1-12c7-4335-8b41-f5c5fa9c6098 spec: sourcePod: network-check-source-869dcfcdcd-w4tzb targetEndpoint: a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T19:08:41Z" message: 'load-balancer-api-internal: tcp connection to a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.110031ms message: 'load-balancer-api-internal: tcp connection to a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:41Z" - latency: 8.983722ms message: 'load-balancer-api-internal: resolved host name a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:44:41Z" - latency: 4.43214ms message: 'load-balancer-api-internal: tcp connection to a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:41Z" - latency: 6.721077ms message: 'load-balancer-api-internal: resolved host name a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:43:41Z" - latency: 4.428246ms message: 'load-balancer-api-internal: tcp connection to a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:41Z" - latency: 8.896928ms message: 'load-balancer-api-internal: resolved host name a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:42:41Z" - latency: 5.222402ms message: 'load-balancer-api-internal: tcp connection to a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:41Z" - latency: 6.467692ms message: 'load-balancer-api-internal: resolved host name a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:41:41Z" - latency: 6.58661ms message: 'load-balancer-api-internal: tcp connection to a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:41Z" - latency: 8.239303ms message: 'load-balancer-api-internal: resolved host name a790e73af19634b90830d82caa542399-1f8253cc512cce2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T19:40:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:02:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-251-to-network-check-target-ip-10-0-131-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-251.ec2.internal uid: 641222cf-9fd5-4a21-a0ed-7d7783cf7f51 resourceVersion: "32430" uid: 19e03eb1-40c1-4f02-83cd-04efcf7e6726 spec: sourcePod: network-check-source-869dcfcdcd-w4tzb targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T19:09:41Z" message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.269303ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:41Z" - latency: 2.192879ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:41Z" - latency: 1.944388ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:41Z" - latency: 2.147927ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:41Z" - latency: 2.212634ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:41Z" - latency: 2.193966ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:39:41Z" - latency: 2.203138ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:38:41Z" - latency: 2.297359ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:37:41Z" - latency: 2.436785ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:36:41Z" - latency: 2.12514ms message: 'network-check-target-ip-10-0-131-123: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:35:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:02:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-251-to-network-check-target-ip-10-0-134-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-251.ec2.internal uid: 641222cf-9fd5-4a21-a0ed-7d7783cf7f51 resourceVersion: "32429" uid: 2ff7b8d7-a0b9-470a-b596-ee60d1bf227b spec: sourcePod: network-check-source-869dcfcdcd-w4tzb targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T19:09:41Z" message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 840.126µs message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:41Z" - latency: 797.575µs message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:41Z" - latency: 788.455µs message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:41Z" - latency: 764.99µs message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:41Z" - latency: 1.142976ms message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:41Z" - latency: 907.008µs message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:39:41Z" - latency: 779.804µs message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:38:41Z" - latency: 1.237167ms message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:37:41Z" - latency: 865.395µs message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:36:41Z" - latency: 745.403µs message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:35:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:02:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-251-to-network-check-target-ip-10-0-139-20 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-251.ec2.internal uid: 641222cf-9fd5-4a21-a0ed-7d7783cf7f51 resourceVersion: "32431" uid: fd30e0d9-fdeb-40c7-9708-e9c742cac44a spec: sourcePod: network-check-source-869dcfcdcd-w4tzb targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T19:09:41Z" message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.987875ms message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:41Z" - latency: 2.354236ms message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:41Z" - latency: 2.111539ms message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:41Z" - latency: 1.988351ms message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:41Z" - latency: 2.208911ms message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:41Z" - latency: 1.998704ms message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:39:41Z" - latency: 2.126143ms message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:38:41Z" - latency: 2.18549ms message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:37:41Z" - latency: 2.198023ms message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:36:41Z" - latency: 2.045345ms message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:35:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T19:02:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-251-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-251.ec2.internal uid: 641222cf-9fd5-4a21-a0ed-7d7783cf7f51 resourceVersion: "32432" uid: bfa02de7-a279-49f3-acdc-5ea096dfaac1 spec: sourcePod: network-check-source-869dcfcdcd-w4tzb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T19:08:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 987.051µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:44:41Z" - latency: 1.634877ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:44:41Z" - latency: 636.155µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:43:41Z" - latency: 1.455926ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:43:41Z" - latency: 846.496µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:42:41Z" - latency: 1.937666ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:42:41Z" - latency: 1.172941ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:41:41Z" - latency: 1.469514ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:41:41Z" - latency: 756.093µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T19:40:41Z" - latency: 1.590042ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T19:40:41Z" kind: List metadata: resourceVersion: ""