apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:42:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-76-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-76.ec2.internal uid: 190f1cb3-f860-4ae2-8c18-4be03b1dcac5 resourceVersion: "18468" uid: da5a9b5d-e0a1-44dc-9a59-d0193caf6cc8 spec: sourcePod: network-check-source-56499946bc-gp8gq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-01T17:49:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 901.453µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:49:33Z" - latency: 957.227µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:48:33Z" - latency: 768.335µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:47:33Z" - latency: 855.194µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:46:33Z" - latency: 799.548µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:45:33Z" - latency: 1.133264ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:44:33Z" - latency: 973.625µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:43:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:42:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-76-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-76.ec2.internal uid: 190f1cb3-f860-4ae2-8c18-4be03b1dcac5 resourceVersion: "22489" uid: 1d32d899-10af-410b-81bf-f67000c44165 spec: sourcePod: network-check-source-56499946bc-gp8gq targetEndpoint: a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T17:48:33Z" message: 'load-balancer-api-external: tcp connection to a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.027907ms message: 'load-balancer-api-external: tcp connection to a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:54:33Z" - latency: 9.176084ms message: 'load-balancer-api-external: resolved host name a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:54:33Z" - latency: 5.081879ms message: 'load-balancer-api-external: tcp connection to a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:53:33Z" - latency: 8.412057ms message: 'load-balancer-api-external: resolved host name a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:53:33Z" - latency: 4.567935ms message: 'load-balancer-api-external: tcp connection to a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:52:33Z" - latency: 8.150314ms message: 'load-balancer-api-external: resolved host name a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:52:33Z" - latency: 5.639806ms message: 'load-balancer-api-external: tcp connection to a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:51:33Z" - latency: 6.864852ms message: 'load-balancer-api-external: resolved host name a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:51:33Z" - latency: 5.513917ms message: 'load-balancer-api-external: tcp connection to a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:50:33Z" - latency: 7.848862ms message: 'load-balancer-api-external: resolved host name a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:50:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:42:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-76-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-76.ec2.internal uid: 190f1cb3-f860-4ae2-8c18-4be03b1dcac5 resourceVersion: "22490" uid: aedfe63e-16fd-473c-84ef-3312d99c391b spec: sourcePod: network-check-source-56499946bc-gp8gq targetEndpoint: a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T17:48:33Z" message: 'load-balancer-api-internal: tcp connection to a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.072166ms message: 'load-balancer-api-internal: tcp connection to a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:54:33Z" - latency: 9.248389ms message: 'load-balancer-api-internal: resolved host name a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:54:33Z" - latency: 4.190874ms message: 'load-balancer-api-internal: tcp connection to a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:53:33Z" - latency: 8.484485ms message: 'load-balancer-api-internal: resolved host name a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:53:33Z" - latency: 4.393441ms message: 'load-balancer-api-internal: tcp connection to a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:52:33Z" - latency: 8.216088ms message: 'load-balancer-api-internal: resolved host name a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:52:33Z" - latency: 5.65092ms message: 'load-balancer-api-internal: tcp connection to a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:51:33Z" - latency: 6.904651ms message: 'load-balancer-api-internal: resolved host name a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:51:33Z" - latency: 5.448823ms message: 'load-balancer-api-internal: tcp connection to a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:50:33Z" - latency: 7.876592ms message: 'load-balancer-api-internal: resolved host name a3afe7eeb304c46d7bce89c121f6e261-4de960e08adf963c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:50:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:42:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-76-to-network-check-target-ip-10-0-131-76 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-76.ec2.internal uid: 190f1cb3-f860-4ae2-8c18-4be03b1dcac5 resourceVersion: "18465" uid: 27bd4bf5-99ee-42a9-8ec4-b26935a6e4d2 spec: sourcePod: network-check-source-56499946bc-gp8gq targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-01T17:49:33Z" message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 769.109µs message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:49:33Z" - latency: 934.764µs message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:48:33Z" - latency: 913.067µs message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:47:33Z" - latency: 957.389µs message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:46:33Z" - latency: 1.363189ms message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:45:33Z" - latency: 1.673631ms message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:44:33Z" - latency: 1.11693ms message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:43:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:42:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-76-to-network-check-target-ip-10-0-140-89 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-76.ec2.internal uid: 190f1cb3-f860-4ae2-8c18-4be03b1dcac5 resourceVersion: "18466" uid: 15c3b149-bd97-4436-9903-e66d9c50bd49 spec: sourcePod: network-check-source-56499946bc-gp8gq targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-01T17:49:33Z" message: 'network-check-target-ip-10-0-140-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.884062ms message: 'network-check-target-ip-10-0-140-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:49:33Z" - latency: 1.859611ms message: 'network-check-target-ip-10-0-140-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:48:33Z" - latency: 1.844578ms message: 'network-check-target-ip-10-0-140-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:47:33Z" - latency: 2.035921ms message: 'network-check-target-ip-10-0-140-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:46:33Z" - latency: 1.67026ms message: 'network-check-target-ip-10-0-140-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:45:33Z" - latency: 1.905654ms message: 'network-check-target-ip-10-0-140-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:44:33Z" - latency: 1.985453ms message: 'network-check-target-ip-10-0-140-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:43:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:42:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-76-to-network-check-target-ip-10-0-143-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-76.ec2.internal uid: 190f1cb3-f860-4ae2-8c18-4be03b1dcac5 resourceVersion: "18467" uid: 7bcbf95a-b25f-4cb1-98fc-0d75dbdd6fa2 spec: sourcePod: network-check-source-56499946bc-gp8gq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-01T17:49:33Z" message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.779331ms message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:49:33Z" - latency: 2.139489ms message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:48:33Z" - latency: 2.489982ms message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:47:33Z" - latency: 2.289517ms message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:46:33Z" - latency: 2.037361ms message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:45:33Z" - latency: 2.157974ms message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:44:33Z" - latency: 2.236016ms message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:43:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:42:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-76-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-76.ec2.internal uid: 190f1cb3-f860-4ae2-8c18-4be03b1dcac5 resourceVersion: "22488" uid: b8e6dada-fb20-4926-8219-d34b02f4e688 spec: sourcePod: network-check-source-56499946bc-gp8gq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-01T17:48:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 827.296µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:54:33Z" - latency: 2.470864ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:54:33Z" - latency: 1.171227ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:53:33Z" - latency: 1.775657ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:53:33Z" - latency: 1.020161ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:52:33Z" - latency: 1.780395ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:52:33Z" - latency: 1.438434ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:51:33Z" - latency: 1.603475ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:51:33Z" - latency: 1.104974ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:50:33Z" - latency: 1.819886ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:50:33Z" kind: List metadata: resourceVersion: ""