apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:02:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-5-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-5.ec2.internal uid: 86964fa9-edc8-4127-bdb6-0e2b03465431 resourceVersion: "60144" uid: 71487cd1-4e45-4913-921a-5cf7a23b67ac spec: sourcePod: network-check-source-869dcfcdcd-cm6s4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T12:09:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.298694ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:44:33Z" - latency: 900.42µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:43:33Z" - latency: 979.616µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:42:33Z" - latency: 933.956µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:41:33Z" - latency: 1.785249ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:40:33Z" - latency: 938.941µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:39:33Z" - latency: 1.139235ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:38:33Z" - latency: 1.704362ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:37:33Z" - latency: 1.0233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:36:33Z" - latency: 1.437602ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:35:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:02:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-5-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-5.ec2.internal uid: 86964fa9-edc8-4127-bdb6-0e2b03465431 resourceVersion: "60146" uid: feb7baef-91a8-44d0-8a8b-d04f269ea508 spec: sourcePod: network-check-source-869dcfcdcd-cm6s4 targetEndpoint: a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T12:08:33Z" message: 'load-balancer-api-external: tcp connection to a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.410719ms message: 'load-balancer-api-external: tcp connection to a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:44:33Z" - latency: 6.277017ms message: 'load-balancer-api-external: resolved host name a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:44:33Z" - latency: 5.272497ms message: 'load-balancer-api-external: tcp connection to a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:43:33Z" - latency: 6.918412ms message: 'load-balancer-api-external: resolved host name a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:43:33Z" - latency: 4.07591ms message: 'load-balancer-api-external: tcp connection to a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:42:33Z" - latency: 6.801466ms message: 'load-balancer-api-external: resolved host name a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:42:33Z" - latency: 4.394134ms message: 'load-balancer-api-external: tcp connection to a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:41:33Z" - latency: 6.50117ms message: 'load-balancer-api-external: resolved host name a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:41:33Z" - latency: 5.885215ms message: 'load-balancer-api-external: tcp connection to a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:40:33Z" - latency: 6.551283ms message: 'load-balancer-api-external: resolved host name a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:40:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:02:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-5-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-5.ec2.internal uid: 86964fa9-edc8-4127-bdb6-0e2b03465431 resourceVersion: "60145" uid: cd67517a-01e2-473d-a893-0ebd7ce0f716 spec: sourcePod: network-check-source-869dcfcdcd-cm6s4 targetEndpoint: a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T12:08:33Z" message: 'load-balancer-api-internal: tcp connection to a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.445139ms message: 'load-balancer-api-internal: tcp connection to a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:44:33Z" - latency: 6.265226ms message: 'load-balancer-api-internal: resolved host name a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:44:33Z" - latency: 5.083587ms message: 'load-balancer-api-internal: tcp connection to a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:43:33Z" - latency: 6.993418ms message: 'load-balancer-api-internal: resolved host name a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:43:33Z" - latency: 4.978514ms message: 'load-balancer-api-internal: tcp connection to a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:42:33Z" - latency: 6.832407ms message: 'load-balancer-api-internal: resolved host name a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:42:33Z" - latency: 4.373732ms message: 'load-balancer-api-internal: tcp connection to a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:41:33Z" - latency: 6.520835ms message: 'load-balancer-api-internal: resolved host name a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:41:33Z" - latency: 5.902004ms message: 'load-balancer-api-internal: tcp connection to a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:40:33Z" - latency: 6.58434ms message: 'load-balancer-api-internal: resolved host name a6b7dcb7b9dd74cc69df19e42d5f3557-55162212e426b39c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T12:40:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:02:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-5-to-network-check-target-ip-10-0-131-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-5.ec2.internal uid: 86964fa9-edc8-4127-bdb6-0e2b03465431 resourceVersion: "60142" uid: f07d3cfd-3070-46a1-88d4-537a73216d77 spec: sourcePod: network-check-source-869dcfcdcd-cm6s4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T12:09:33Z" message: 'network-check-target-ip-10-0-131-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.212339ms message: 'network-check-target-ip-10-0-131-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:44:33Z" - latency: 2.084995ms message: 'network-check-target-ip-10-0-131-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:43:33Z" - latency: 2.326597ms message: 'network-check-target-ip-10-0-131-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:42:33Z" - latency: 2.201261ms message: 'network-check-target-ip-10-0-131-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:41:33Z" - latency: 2.823278ms message: 'network-check-target-ip-10-0-131-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:40:33Z" - latency: 2.360351ms message: 'network-check-target-ip-10-0-131-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:39:33Z" - latency: 1.905375ms message: 'network-check-target-ip-10-0-131-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:38:33Z" - latency: 2.873403ms message: 'network-check-target-ip-10-0-131-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:37:33Z" - latency: 2.386894ms message: 'network-check-target-ip-10-0-131-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:36:33Z" - latency: 2.328725ms message: 'network-check-target-ip-10-0-131-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:35:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:02:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-5-to-network-check-target-ip-10-0-135-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-5.ec2.internal uid: 86964fa9-edc8-4127-bdb6-0e2b03465431 resourceVersion: "60141" uid: 4e4ae060-46dc-419e-bf0d-8676acf76ef5 spec: sourcePod: network-check-source-869dcfcdcd-cm6s4 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T12:09:33Z" message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.180134ms message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:44:33Z" - latency: 2.123231ms message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:43:33Z" - latency: 2.122347ms message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:42:33Z" - latency: 2.224677ms message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:41:33Z" - latency: 2.207855ms message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:40:33Z" - latency: 2.281109ms message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:39:33Z" - latency: 2.381041ms message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:38:33Z" - latency: 2.323938ms message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:37:33Z" - latency: 2.675378ms message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:36:33Z" - latency: 2.263059ms message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:35:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:02:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-5-to-network-check-target-ip-10-0-139-5 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-5.ec2.internal uid: 86964fa9-edc8-4127-bdb6-0e2b03465431 resourceVersion: "60140" uid: e333dc82-5ea2-414d-b588-045c7fe32b58 spec: sourcePod: network-check-source-869dcfcdcd-cm6s4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T12:09:33Z" message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 856.517µs message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:44:33Z" - latency: 886.434µs message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:43:33Z" - latency: 1.245702ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:42:33Z" - latency: 1.000173ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:41:33Z" - latency: 1.351121ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:40:33Z" - latency: 765.687µs message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:39:33Z" - latency: 936.7µs message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:38:33Z" - latency: 737.199µs message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:37:33Z" - latency: 985.783µs message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:36:33Z" - latency: 1.001191ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:35:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T12:02:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-5-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-5.ec2.internal uid: 86964fa9-edc8-4127-bdb6-0e2b03465431 resourceVersion: "60143" uid: 8b796f88-3853-4938-ba4a-7f81cdb7be64 spec: sourcePod: network-check-source-869dcfcdcd-cm6s4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T12:08:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 997.59µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:44:33Z" - latency: 1.826059ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T12:44:33Z" - latency: 876.465µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:43:33Z" - latency: 1.721077ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T12:43:33Z" - latency: 1.009418ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:42:33Z" - latency: 1.705297ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T12:42:33Z" - latency: 1.408242ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:41:33Z" - latency: 1.644993ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T12:41:33Z" - latency: 1.016632ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T12:40:33Z" - latency: 2.099438ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T12:40:33Z" kind: List metadata: resourceVersion: ""