apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T00:21:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: 0490f331-6dcd-404c-9ce9-49291635c64a resourceVersion: "56086" uid: 9049c8c5-cec3-4873-981b-dbffdb5e2313 spec: sourcePod: network-check-source-869dcfcdcd-kkbl9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T00:28:46Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 948.613µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:56:46Z" - latency: 1.143628ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:55:46Z" - latency: 998.177µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:54:46Z" - latency: 1.447542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:53:46Z" - latency: 843.422µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:52:46Z" - latency: 1.201284ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:51:46Z" - latency: 988.065µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:50:46Z" - latency: 882.856µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:49:46Z" - latency: 1.086127ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:48:46Z" - latency: 1.095457ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:47:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T00:21:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: 0490f331-6dcd-404c-9ce9-49291635c64a resourceVersion: "57182" uid: f8cc8b38-fe7b-4ef7-bddf-38c78cda258e spec: sourcePod: network-check-source-869dcfcdcd-kkbl9 targetEndpoint: a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T00:27:46Z" message: 'load-balancer-api-external: tcp connection to a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.597526ms message: 'load-balancer-api-external: tcp connection to a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:57:46Z" - latency: 7.452628ms message: 'load-balancer-api-external: resolved host name a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T00:57:46Z" - latency: 4.248719ms message: 'load-balancer-api-external: tcp connection to a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:56:46Z" - latency: 7.075351ms message: 'load-balancer-api-external: resolved host name a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T00:56:46Z" - latency: 3.993663ms message: 'load-balancer-api-external: tcp connection to a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:55:46Z" - latency: 6.420592ms message: 'load-balancer-api-external: resolved host name a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T00:55:46Z" - latency: 4.05302ms message: 'load-balancer-api-external: tcp connection to a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:54:46Z" - latency: 7.083105ms message: 'load-balancer-api-external: resolved host name a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T00:54:46Z" - latency: 6.499728ms message: 'load-balancer-api-external: tcp connection to a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:53:46Z" - latency: 7.126426ms message: 'load-balancer-api-external: resolved host name a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T00:53:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T00:21:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: 0490f331-6dcd-404c-9ce9-49291635c64a resourceVersion: "57183" uid: 01fb531f-25cf-4bbe-96d0-ef6f381b122d spec: sourcePod: network-check-source-869dcfcdcd-kkbl9 targetEndpoint: a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T00:27:46Z" message: 'load-balancer-api-internal: tcp connection to a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.040149ms message: 'load-balancer-api-internal: tcp connection to a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:57:46Z" - latency: 7.485973ms message: 'load-balancer-api-internal: resolved host name a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T00:57:46Z" - latency: 3.870601ms message: 'load-balancer-api-internal: tcp connection to a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:56:46Z" - latency: 7.007931ms message: 'load-balancer-api-internal: resolved host name a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T00:56:46Z" - latency: 5.300725ms message: 'load-balancer-api-internal: tcp connection to a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:55:46Z" - latency: 6.38523ms message: 'load-balancer-api-internal: resolved host name a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T00:55:46Z" - latency: 5.604483ms message: 'load-balancer-api-internal: tcp connection to a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:54:46Z" - latency: 7.050189ms message: 'load-balancer-api-internal: resolved host name a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T00:54:46Z" - latency: 5.755342ms message: 'load-balancer-api-internal: tcp connection to a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:53:46Z" - latency: 7.200483ms message: 'load-balancer-api-internal: resolved host name a45eb6cee5e994ff5ac84366383cf98d-050037739b05daaa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T00:53:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T00:21:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-network-check-target-ip-10-0-128-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: 0490f331-6dcd-404c-9ce9-49291635c64a resourceVersion: "56084" uid: cd646ec3-1737-4a90-9d37-76e312143b3c spec: sourcePod: network-check-source-869dcfcdcd-kkbl9 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T00:28:46Z" message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.344923ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:56:46Z" - latency: 2.21538ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:55:46Z" - latency: 2.62908ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:54:46Z" - latency: 2.47394ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:53:46Z" - latency: 2.238147ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:52:46Z" - latency: 2.122513ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:51:46Z" - latency: 2.076852ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:50:46Z" - latency: 2.402093ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:49:46Z" - latency: 2.284957ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:48:46Z" - latency: 2.561355ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:47:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T00:21:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-network-check-target-ip-10-0-135-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: 0490f331-6dcd-404c-9ce9-49291635c64a resourceVersion: "56083" uid: 85fa3d6f-0a01-43b0-a147-a2493fc818a6 spec: sourcePod: network-check-source-869dcfcdcd-kkbl9 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T00:28:46Z" message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 920.019µs message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:56:46Z" - latency: 935.471µs message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:55:46Z" - latency: 1.106258ms message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:54:46Z" - latency: 989.78µs message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:53:46Z" - latency: 928.759µs message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:52:46Z" - latency: 1.46417ms message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:51:46Z" - latency: 1.500751ms message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:50:46Z" - latency: 1.068057ms message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:49:46Z" - latency: 1.084928ms message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:48:46Z" - latency: 1.052085ms message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:47:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T00:21:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-network-check-target-ip-10-0-137-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: 0490f331-6dcd-404c-9ce9-49291635c64a resourceVersion: "56085" uid: 4261368d-c86d-4a50-9ce0-9604babcd5d5 spec: sourcePod: network-check-source-869dcfcdcd-kkbl9 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T00:28:46Z" message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.394607ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:56:46Z" - latency: 2.2925ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:55:46Z" - latency: 2.363744ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:54:46Z" - latency: 2.443767ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:53:46Z" - latency: 2.17598ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:52:46Z" - latency: 2.432382ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:51:46Z" - latency: 2.269156ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:50:46Z" - latency: 2.147422ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:49:46Z" - latency: 2.529236ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:48:46Z" - latency: 2.488951ms message: 'network-check-target-ip-10-0-137-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:47:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T00:21:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: 0490f331-6dcd-404c-9ce9-49291635c64a resourceVersion: "57180" uid: 5de28512-d858-4377-8769-813bd6380b8d spec: sourcePod: network-check-source-869dcfcdcd-kkbl9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T00:27:46Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 833.185µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:57:46Z" - latency: 1.7954ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T00:57:46Z" - latency: 839.054µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:56:46Z" - latency: 1.80524ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T00:56:46Z" - latency: 1.006045ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:55:46Z" - latency: 1.68629ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T00:55:46Z" - latency: 998.566µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:54:46Z" - latency: 1.843758ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T00:54:46Z" - latency: 838.124µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T00:53:46Z" - latency: 1.718974ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T00:53:46Z" kind: List metadata: resourceVersion: ""