apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:46:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-253-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-253.ec2.internal uid: 6192fb80-c9d3-4c0c-af72-7ea91dcfdb9c resourceVersion: "20759" uid: c7a2f29b-c325-470e-bf01-93aa739562e1 spec: sourcePod: network-check-source-dbd9cf844-mrvkz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T11:53:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 895.933µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:07:24Z" - latency: 1.211966ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:06:24Z" - latency: 1.151905ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:05:24Z" - latency: 847.592µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:04:24Z" - latency: 886.609µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:03:24Z" - latency: 825.285µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:02:24Z" - latency: 820.362µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:01:24Z" - latency: 965.255µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:00:24Z" - latency: 785.085µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:59:24Z" - latency: 1.220247ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:58:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:46:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-253-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-253.ec2.internal uid: 6192fb80-c9d3-4c0c-af72-7ea91dcfdb9c resourceVersion: "22185" uid: 1f900ceb-ce4e-4be8-b951-0d41fd022300 spec: sourcePod: network-check-source-dbd9cf844-mrvkz targetEndpoint: acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T11:52:24Z" message: 'load-balancer-api-external: tcp connection to acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.304085ms message: 'load-balancer-api-external: tcp connection to acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:10:24Z" - latency: 8.572195ms message: 'load-balancer-api-external: resolved host name acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:10:24Z" - latency: 4.733069ms message: 'load-balancer-api-external: tcp connection to acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:09:24Z" - latency: 8.188951ms message: 'load-balancer-api-external: resolved host name acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:09:24Z" - latency: 5.350683ms message: 'load-balancer-api-external: tcp connection to acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:08:24Z" - latency: 8.386255ms message: 'load-balancer-api-external: resolved host name acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:08:24Z" - latency: 4.969284ms message: 'load-balancer-api-external: tcp connection to acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:07:24Z" - latency: 8.033785ms message: 'load-balancer-api-external: resolved host name acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:07:24Z" - latency: 3.794326ms message: 'load-balancer-api-external: tcp connection to acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:06:24Z" - latency: 10.09883ms message: 'load-balancer-api-external: resolved host name acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:06:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:46:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-253-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-253.ec2.internal uid: 6192fb80-c9d3-4c0c-af72-7ea91dcfdb9c resourceVersion: "22184" uid: ae5f635a-94db-4944-bba2-458a2ae47a60 spec: sourcePod: network-check-source-dbd9cf844-mrvkz targetEndpoint: acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T11:52:24Z" message: 'load-balancer-api-internal: tcp connection to acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.275287ms message: 'load-balancer-api-internal: tcp connection to acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:10:24Z" - latency: 8.594012ms message: 'load-balancer-api-internal: resolved host name acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:10:24Z" - latency: 4.884234ms message: 'load-balancer-api-internal: tcp connection to acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:09:24Z" - latency: 8.234777ms message: 'load-balancer-api-internal: resolved host name acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:09:24Z" - latency: 5.933894ms message: 'load-balancer-api-internal: tcp connection to acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:08:24Z" - latency: 8.373289ms message: 'load-balancer-api-internal: resolved host name acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:08:24Z" - latency: 4.959609ms message: 'load-balancer-api-internal: tcp connection to acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:07:24Z" - latency: 8.12531ms message: 'load-balancer-api-internal: resolved host name acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:07:24Z" - latency: 3.882998ms message: 'load-balancer-api-internal: tcp connection to acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:06:24Z" - latency: 10.032639ms message: 'load-balancer-api-internal: resolved host name acb5ecb31344b4fa6b851e137df902f9-8842c2c9e4b01d62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:06:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:46:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-253-to-network-check-target-ip-10-0-132-76 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-253.ec2.internal uid: 6192fb80-c9d3-4c0c-af72-7ea91dcfdb9c resourceVersion: "20757" uid: 64a1baa3-0acb-4562-b96f-9e234eec1551 spec: sourcePod: network-check-source-dbd9cf844-mrvkz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-08T11:53:24Z" message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.261679ms message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:07:24Z" - latency: 2.14675ms message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:06:24Z" - latency: 2.242199ms message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:05:24Z" - latency: 1.984642ms message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:04:24Z" - latency: 2.234512ms message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:03:24Z" - latency: 2.207007ms message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:02:24Z" - latency: 2.43662ms message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:01:24Z" - latency: 2.276101ms message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:00:24Z" - latency: 1.936616ms message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:59:24Z" - latency: 2.170531ms message: 'network-check-target-ip-10-0-132-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:58:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:46:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-253-to-network-check-target-ip-10-0-135-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-253.ec2.internal uid: 6192fb80-c9d3-4c0c-af72-7ea91dcfdb9c resourceVersion: "20756" uid: 03d64191-1fc3-42e0-a508-dd4c1f9c190c spec: sourcePod: network-check-source-dbd9cf844-mrvkz targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-08T11:53:24Z" message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 823.1µs message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:07:24Z" - latency: 1.507271ms message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:06:24Z" - latency: 1.372115ms message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:05:24Z" - latency: 1.261865ms message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:04:24Z" - latency: 994.771µs message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:03:24Z" - latency: 853.318µs message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:02:24Z" - latency: 1.211045ms message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:01:24Z" - latency: 829.83µs message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:00:24Z" - latency: 739.799µs message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:59:24Z" - latency: 748.009µs message: 'network-check-target-ip-10-0-135-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:58:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:46:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-253-to-network-check-target-ip-10-0-137-95 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-253.ec2.internal uid: 6192fb80-c9d3-4c0c-af72-7ea91dcfdb9c resourceVersion: "20758" uid: 4d3d74f2-d3f7-4e99-81dd-a13ab8ffb2aa spec: sourcePod: network-check-source-dbd9cf844-mrvkz targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T11:53:24Z" message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.294352ms message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:07:24Z" - latency: 2.187719ms message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:06:24Z" - latency: 2.174198ms message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:05:24Z" - latency: 2.597242ms message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:04:24Z" - latency: 2.220609ms message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:03:24Z" - latency: 2.158875ms message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:02:24Z" - latency: 2.445226ms message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:01:24Z" - latency: 2.2781ms message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:00:24Z" - latency: 2.284213ms message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:59:24Z" - latency: 2.531012ms message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:58:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:46:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-253-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-253.ec2.internal uid: 6192fb80-c9d3-4c0c-af72-7ea91dcfdb9c resourceVersion: "22183" uid: e982a4b8-9b7f-4c87-9092-19d2e81753c7 spec: sourcePod: network-check-source-dbd9cf844-mrvkz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T11:52:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 992.759µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:10:24Z" - latency: 1.89248ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:10:24Z" - latency: 1.156769ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:09:24Z" - latency: 1.773127ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:09:24Z" - latency: 1.306603ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:08:24Z" - latency: 1.694775ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:08:24Z" - latency: 1.315365ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:07:24Z" - latency: 1.936737ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:07:24Z" - latency: 810.042µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:06:24Z" - latency: 2.012518ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:06:24Z" kind: List metadata: resourceVersion: ""