apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:28:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-93-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-93.ec2.internal uid: 25311083-e421-4112-afcb-635309a1dbc6 resourceVersion: "63787" uid: f8a5bc8b-caf4-477a-9ed1-d01607cb8939 spec: sourcePod: network-check-source-7d88cb55d8-hmpdp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T14:35:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.263436ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:10:31Z" - latency: 1.188278ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:09:31Z" - latency: 1.531334ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:08:31Z" - latency: 822.414µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:07:31Z" - latency: 1.354968ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:06:31Z" - latency: 1.260645ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:05:31Z" - latency: 784.128µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:04:31Z" - latency: 1.000562ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:03:31Z" - latency: 1.145004ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:02:31Z" - latency: 1.136968ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:01:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:28:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-93-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-93.ec2.internal uid: 25311083-e421-4112-afcb-635309a1dbc6 resourceVersion: "63788" uid: 96d3b55d-008d-4b6a-b472-0d6108bdb8dd spec: sourcePod: network-check-source-7d88cb55d8-hmpdp targetEndpoint: aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T14:34:31Z" message: 'load-balancer-api-external: tcp connection to aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.826985ms message: 'load-balancer-api-external: tcp connection to aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:10:31Z" - latency: 6.805143ms message: 'load-balancer-api-external: resolved host name aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:10:31Z" - latency: 5.90406ms message: 'load-balancer-api-external: tcp connection to aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:09:31Z" - latency: 6.83934ms message: 'load-balancer-api-external: resolved host name aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:09:31Z" - latency: 4.034996ms message: 'load-balancer-api-external: tcp connection to aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:08:31Z" - latency: 9.29857ms message: 'load-balancer-api-external: resolved host name aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:08:31Z" - latency: 4.720448ms message: 'load-balancer-api-external: tcp connection to aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:07:31Z" - latency: 6.852432ms message: 'load-balancer-api-external: resolved host name aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:07:31Z" - latency: 4.485463ms message: 'load-balancer-api-external: tcp connection to aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:06:31Z" - latency: 7.215961ms message: 'load-balancer-api-external: resolved host name aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:06:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:28:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-93-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-93.ec2.internal uid: 25311083-e421-4112-afcb-635309a1dbc6 resourceVersion: "63789" uid: c99bdb3a-e049-4bc4-a227-dcc48dd5caac spec: sourcePod: network-check-source-7d88cb55d8-hmpdp targetEndpoint: aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T14:34:31Z" message: 'load-balancer-api-internal: tcp connection to aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.464846ms message: 'load-balancer-api-internal: tcp connection to aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:10:31Z" - latency: 6.723296ms message: 'load-balancer-api-internal: resolved host name aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:10:31Z" - latency: 4.417852ms message: 'load-balancer-api-internal: tcp connection to aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:09:31Z" - latency: 6.873782ms message: 'load-balancer-api-internal: resolved host name aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:09:31Z" - latency: 5.105581ms message: 'load-balancer-api-internal: tcp connection to aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:08:31Z" - latency: 9.178785ms message: 'load-balancer-api-internal: resolved host name aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:08:31Z" - latency: 4.131927ms message: 'load-balancer-api-internal: tcp connection to aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:07:31Z" - latency: 6.901532ms message: 'load-balancer-api-internal: resolved host name aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:07:31Z" - latency: 4.422529ms message: 'load-balancer-api-internal: tcp connection to aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:06:31Z" - latency: 7.028566ms message: 'load-balancer-api-internal: resolved host name aa283e1719c184c578c73d94a955d45a-8e4332cfc2f533c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:06:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:28:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-93-to-network-check-target-ip-10-0-132-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-93.ec2.internal uid: 25311083-e421-4112-afcb-635309a1dbc6 resourceVersion: "63784" uid: 7878484d-3b59-424e-be65-74e118681ce1 spec: sourcePod: network-check-source-7d88cb55d8-hmpdp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T14:35:31Z" message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.068336ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:10:31Z" - latency: 1.980852ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:09:31Z" - latency: 2.041237ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:08:31Z" - latency: 2.027603ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:07:31Z" - latency: 2.251628ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:06:31Z" - latency: 1.940778ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:05:31Z" - latency: 1.843242ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:04:31Z" - latency: 1.994179ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:03:31Z" - latency: 1.963038ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:02:31Z" - latency: 2.034008ms message: 'network-check-target-ip-10-0-132-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:01:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:28:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-93-to-network-check-target-ip-10-0-134-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-93.ec2.internal uid: 25311083-e421-4112-afcb-635309a1dbc6 resourceVersion: "63785" uid: f2af635f-211a-496b-900a-a6d9e8985127 spec: sourcePod: network-check-source-7d88cb55d8-hmpdp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T14:35:31Z" message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.345481ms message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:10:31Z" - latency: 2.352389ms message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:09:31Z" - latency: 1.930696ms message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:08:31Z" - latency: 2.067602ms message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:07:31Z" - latency: 2.562807ms message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:06:31Z" - latency: 2.276037ms message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:05:31Z" - latency: 2.131886ms message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:04:31Z" - latency: 2.330065ms message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:03:31Z" - latency: 2.370155ms message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:02:31Z" - latency: 2.335342ms message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:01:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:28:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-93-to-network-check-target-ip-10-0-135-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-93.ec2.internal uid: 25311083-e421-4112-afcb-635309a1dbc6 resourceVersion: "63783" uid: d848cf69-0aaa-479a-8cb1-0ee11eded7ce spec: sourcePod: network-check-source-7d88cb55d8-hmpdp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T14:35:31Z" message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 901.379µs message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:10:31Z" - latency: 1.124335ms message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:09:31Z" - latency: 1.120779ms message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:08:31Z" - latency: 961.312µs message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:07:31Z" - latency: 1.678218ms message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:06:31Z" - latency: 902.211µs message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:05:31Z" - latency: 993.36µs message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:04:31Z" - latency: 1.049416ms message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:03:31Z" - latency: 1.33197ms message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:02:31Z" - latency: 999.838µs message: 'network-check-target-ip-10-0-135-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:01:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:28:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-93-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-93.ec2.internal uid: 25311083-e421-4112-afcb-635309a1dbc6 resourceVersion: "63786" uid: 86e60b31-2692-473d-8017-fcfbbb9fcb60 spec: sourcePod: network-check-source-7d88cb55d8-hmpdp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T14:34:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.202104ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:10:31Z" - latency: 1.926238ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:10:31Z" - latency: 1.115308ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:09:31Z" - latency: 1.957086ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:09:31Z" - latency: 873.245µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:08:31Z" - latency: 2.408686ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:08:31Z" - latency: 798.385µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:07:31Z" - latency: 1.660464ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:07:31Z" - latency: 970.097µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:06:31Z" - latency: 2.215624ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:06:31Z" kind: List metadata: resourceVersion: ""