apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T17:09:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-233-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-233.ec2.internal uid: 140f4d5d-e53d-4d36-9ace-3a6c05c8ff9d resourceVersion: "64393" uid: 11838a7e-8d6e-4a6f-917b-aec5c58e7d21 spec: sourcePod: network-check-source-7d88cb55d8-c2v6b targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T17:16:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 759.44µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:51:52Z" - latency: 1.063802ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:50:52Z" - latency: 970.404µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:49:52Z" - latency: 1.13273ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:48:52Z" - latency: 1.186175ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:47:52Z" - latency: 1.157091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:46:52Z" - latency: 1.199898ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:45:52Z" - latency: 1.234306ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:44:52Z" - latency: 1.129681ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:43:52Z" - latency: 1.184995ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:42:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T17:09:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-233-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-233.ec2.internal uid: 140f4d5d-e53d-4d36-9ace-3a6c05c8ff9d resourceVersion: "64395" uid: 76fa41a4-0d87-46d5-a28e-7f8568563c5d spec: sourcePod: network-check-source-7d88cb55d8-c2v6b targetEndpoint: a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T17:15:52Z" message: 'load-balancer-api-external: tcp connection to a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.217514ms message: 'load-balancer-api-external: tcp connection to a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:51:52Z" - latency: 8.380584ms message: 'load-balancer-api-external: resolved host name a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:51:52Z" - latency: 4.224183ms message: 'load-balancer-api-external: tcp connection to a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:50:52Z" - latency: 8.773831ms message: 'load-balancer-api-external: resolved host name a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:50:52Z" - latency: 4.865156ms message: 'load-balancer-api-external: tcp connection to a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:49:52Z" - latency: 7.789569ms message: 'load-balancer-api-external: resolved host name a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:49:52Z" - latency: 3.780825ms message: 'load-balancer-api-external: tcp connection to a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:48:52Z" - latency: 8.858558ms message: 'load-balancer-api-external: resolved host name a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:48:52Z" - latency: 3.65818ms message: 'load-balancer-api-external: tcp connection to a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:47:52Z" - latency: 9.240178ms message: 'load-balancer-api-external: resolved host name a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:47:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T17:09:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-233-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-233.ec2.internal uid: 140f4d5d-e53d-4d36-9ace-3a6c05c8ff9d resourceVersion: "64394" uid: 63f505df-b752-4383-98fa-217c4227211d spec: sourcePod: network-check-source-7d88cb55d8-c2v6b targetEndpoint: a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T17:15:52Z" message: 'load-balancer-api-internal: tcp connection to a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.258629ms message: 'load-balancer-api-internal: tcp connection to a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:51:52Z" - latency: 8.433771ms message: 'load-balancer-api-internal: resolved host name a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:51:52Z" - latency: 4.24942ms message: 'load-balancer-api-internal: tcp connection to a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:50:52Z" - latency: 8.747001ms message: 'load-balancer-api-internal: resolved host name a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:50:52Z" - latency: 4.840976ms message: 'load-balancer-api-internal: tcp connection to a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:49:52Z" - latency: 7.715463ms message: 'load-balancer-api-internal: resolved host name a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:49:52Z" - latency: 3.775926ms message: 'load-balancer-api-internal: tcp connection to a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:48:52Z" - latency: 8.781848ms message: 'load-balancer-api-internal: resolved host name a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:48:52Z" - latency: 3.671457ms message: 'load-balancer-api-internal: tcp connection to a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:47:52Z" - latency: 9.176373ms message: 'load-balancer-api-internal: resolved host name a73580e5cd06c400d9a98dbcb4ff0bde-8c1a04994d0ed188.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:47:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T17:09:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-233-to-network-check-target-ip-10-0-135-233 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-233.ec2.internal uid: 140f4d5d-e53d-4d36-9ace-3a6c05c8ff9d resourceVersion: "64389" uid: ae5d2bd8-383e-47ac-befe-4b018102b5a0 spec: sourcePod: network-check-source-7d88cb55d8-c2v6b targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T17:16:52Z" message: 'network-check-target-ip-10-0-135-233: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.249127ms message: 'network-check-target-ip-10-0-135-233: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:51:52Z" - latency: 1.133728ms message: 'network-check-target-ip-10-0-135-233: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:50:52Z" - latency: 1.188165ms message: 'network-check-target-ip-10-0-135-233: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:49:52Z" - latency: 1.080034ms message: 'network-check-target-ip-10-0-135-233: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:48:52Z" - latency: 885.425µs message: 'network-check-target-ip-10-0-135-233: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:47:52Z" - latency: 1.109521ms message: 'network-check-target-ip-10-0-135-233: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:46:52Z" - latency: 916.055µs message: 'network-check-target-ip-10-0-135-233: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:45:52Z" - latency: 816.546µs message: 'network-check-target-ip-10-0-135-233: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:44:52Z" - latency: 1.003778ms message: 'network-check-target-ip-10-0-135-233: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:43:52Z" - latency: 1.198247ms message: 'network-check-target-ip-10-0-135-233: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:42:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T17:09:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-233-to-network-check-target-ip-10-0-139-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-233.ec2.internal uid: 140f4d5d-e53d-4d36-9ace-3a6c05c8ff9d resourceVersion: "64391" uid: 26a0a3e1-751f-4700-8f4b-b0a777547951 spec: sourcePod: network-check-source-7d88cb55d8-c2v6b targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T17:16:52Z" message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.26382ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:51:52Z" - latency: 1.999649ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:50:52Z" - latency: 2.240076ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:49:52Z" - latency: 2.406045ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:48:52Z" - latency: 2.402035ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:47:52Z" - latency: 2.289471ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:46:52Z" - latency: 2.200175ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:45:52Z" - latency: 2.179398ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:44:52Z" - latency: 2.695824ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:43:52Z" - latency: 2.184226ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:42:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T17:09:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-233-to-network-check-target-ip-10-0-140-80 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-233.ec2.internal uid: 140f4d5d-e53d-4d36-9ace-3a6c05c8ff9d resourceVersion: "64390" uid: fb921a6b-46bf-41f9-87f1-789db12e36d6 spec: sourcePod: network-check-source-7d88cb55d8-c2v6b targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T17:16:52Z" message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.134959ms message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:51:52Z" - latency: 1.913302ms message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:50:52Z" - latency: 2.040191ms message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:49:52Z" - latency: 1.975376ms message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:48:52Z" - latency: 1.876713ms message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:47:52Z" - latency: 1.92358ms message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:46:52Z" - latency: 1.646155ms message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:45:52Z" - latency: 1.90266ms message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:44:52Z" - latency: 2.127662ms message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:43:52Z" - latency: 2.246179ms message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:42:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T17:09:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-233-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-233.ec2.internal uid: 140f4d5d-e53d-4d36-9ace-3a6c05c8ff9d resourceVersion: "64392" uid: cecc7c19-79b8-4290-a846-231d620a4ff3 spec: sourcePod: network-check-source-7d88cb55d8-c2v6b targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T17:15:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 765.462µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:51:52Z" - latency: 2.112164ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T17:51:52Z" - latency: 958.902µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:50:52Z" - latency: 1.859171ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T17:50:52Z" - latency: 843.65µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:49:52Z" - latency: 1.615576ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T17:49:52Z" - latency: 951.308µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:48:52Z" - latency: 1.844204ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T17:48:52Z" - latency: 848.163µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:47:52Z" - latency: 1.655328ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T17:47:52Z" kind: List metadata: resourceVersion: ""