apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T15:53:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-224-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-224.ec2.internal uid: 263ec6ff-d37b-47d7-aa15-31a94908eb9f resourceVersion: "85303" uid: 6cd500dd-af97-41eb-985f-07ea98984216 spec: sourcePod: network-check-source-7d88cb55d8-w7s6n targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-26T16:00:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 804.988µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:42:19Z" - latency: 993.536µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:41:19Z" - latency: 1.305678ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:40:19Z" - latency: 1.47881ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:39:19Z" - latency: 1.090099ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:38:19Z" - latency: 888.068µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:37:19Z" - latency: 1.211045ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:36:19Z" - latency: 851.332µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:35:19Z" - latency: 1.084709ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:34:19Z" - latency: 973.531µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:33:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T15:53:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-224-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-224.ec2.internal uid: 263ec6ff-d37b-47d7-aa15-31a94908eb9f resourceVersion: "83321" uid: 02ddb0f8-e9c0-4967-95c7-d72df371c1af spec: sourcePod: network-check-source-7d88cb55d8-w7s6n targetEndpoint: ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-26T15:59:19Z" message: 'load-balancer-api-external: tcp connection to ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.633233ms message: 'load-balancer-api-external: tcp connection to ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:41:19Z" - latency: 7.344304ms message: 'load-balancer-api-external: resolved host name ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:41:19Z" - latency: 5.066619ms message: 'load-balancer-api-external: tcp connection to ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:40:19Z" - latency: 7.278059ms message: 'load-balancer-api-external: resolved host name ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:40:19Z" - latency: 21.974905ms message: 'load-balancer-api-external: tcp connection to ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:39:19Z" - latency: 7.802217ms message: 'load-balancer-api-external: resolved host name ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:39:19Z" - latency: 3.353386ms message: 'load-balancer-api-external: tcp connection to ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:38:19Z" - latency: 6.859211ms message: 'load-balancer-api-external: resolved host name ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:38:19Z" - latency: 4.090067ms message: 'load-balancer-api-external: tcp connection to ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:37:19Z" - latency: 7.184649ms message: 'load-balancer-api-external: resolved host name ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:37:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T15:53:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-224-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-224.ec2.internal uid: 263ec6ff-d37b-47d7-aa15-31a94908eb9f resourceVersion: "83320" uid: d50f63c6-b367-472f-badd-4e1cd483a771 spec: sourcePod: network-check-source-7d88cb55d8-w7s6n targetEndpoint: ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-26T15:59:19Z" message: 'load-balancer-api-internal: tcp connection to ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.600396ms message: 'load-balancer-api-internal: tcp connection to ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:41:19Z" - latency: 7.402549ms message: 'load-balancer-api-internal: resolved host name ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:41:19Z" - latency: 5.059314ms message: 'load-balancer-api-internal: tcp connection to ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:40:19Z" - latency: 7.309144ms message: 'load-balancer-api-internal: resolved host name ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:40:19Z" - latency: 5.823901ms message: 'load-balancer-api-internal: tcp connection to ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:39:19Z" - latency: 7.538493ms message: 'load-balancer-api-internal: resolved host name ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:39:19Z" - latency: 3.370528ms message: 'load-balancer-api-internal: tcp connection to ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:38:19Z" - latency: 6.907649ms message: 'load-balancer-api-internal: resolved host name ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:38:19Z" - latency: 3.481797ms message: 'load-balancer-api-internal: tcp connection to ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:37:19Z" - latency: 7.122644ms message: 'load-balancer-api-internal: resolved host name ace83d4c19a2d4f4d878d8f6833c415b-fa90b9b2de4e607d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:37:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T15:53:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-224-to-network-check-target-ip-10-0-128-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-224.ec2.internal uid: 263ec6ff-d37b-47d7-aa15-31a94908eb9f resourceVersion: "85300" uid: b9059c46-b5f5-4292-9808-35b64f33c913 spec: sourcePod: network-check-source-7d88cb55d8-w7s6n targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-26T16:00:19Z" message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.923191ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:42:19Z" - latency: 2.406667ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:41:19Z" - latency: 1.947804ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:40:19Z" - latency: 2.189294ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:39:19Z" - latency: 2.088918ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:38:19Z" - latency: 2.117244ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:37:19Z" - latency: 1.976581ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:36:19Z" - latency: 2.910287ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:35:19Z" - latency: 2.056586ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:34:19Z" - latency: 2.163699ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:33:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T15:53:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-224-to-network-check-target-ip-10-0-133-204 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-224.ec2.internal uid: 263ec6ff-d37b-47d7-aa15-31a94908eb9f resourceVersion: "85302" uid: f1765470-0a31-4f26-891a-7071f8c00ed8 spec: sourcePod: network-check-source-7d88cb55d8-w7s6n targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-26T16:00:19Z" message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.589251ms message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:42:19Z" - latency: 1.647981ms message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:41:19Z" - latency: 2.317284ms message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:40:19Z" - latency: 2.108313ms message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:39:19Z" - latency: 1.742174ms message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:38:19Z" - latency: 1.621385ms message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:37:19Z" - latency: 1.979181ms message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:36:19Z" - latency: 2.781682ms message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:35:19Z" - latency: 1.990001ms message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:34:19Z" - latency: 2.086492ms message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:33:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T15:53:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-224-to-network-check-target-ip-10-0-142-224 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-224.ec2.internal uid: 263ec6ff-d37b-47d7-aa15-31a94908eb9f resourceVersion: "85301" uid: fc531ccb-fd88-411f-8bbe-de7ab226e6a3 spec: sourcePod: network-check-source-7d88cb55d8-w7s6n targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-26T16:00:19Z" message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.261389ms message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:42:19Z" - latency: 849.312µs message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:41:19Z" - latency: 957.23µs message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:40:19Z" - latency: 1.563207ms message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:39:19Z" - latency: 977.961µs message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:38:19Z" - latency: 933.386µs message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:37:19Z" - latency: 1.447618ms message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:36:19Z" - latency: 1.047854ms message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:35:19Z" - latency: 938.496µs message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:34:19Z" - latency: 1.335588ms message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:33:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T15:53:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-224-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-224.ec2.internal uid: 263ec6ff-d37b-47d7-aa15-31a94908eb9f resourceVersion: "83319" uid: b8c78dac-3c59-47a5-9ee5-bc4d86236804 spec: sourcePod: network-check-source-7d88cb55d8-w7s6n targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-26T15:59:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.135675ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:41:19Z" - latency: 1.78851ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T16:41:19Z" - latency: 1.278002ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:40:19Z" - latency: 1.907321ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T16:40:19Z" - latency: 1.06521ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:39:19Z" - latency: 1.988844ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T16:39:19Z" - latency: 1.182746ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:38:19Z" - latency: 1.739195ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T16:38:19Z" - latency: 844.835µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:37:19Z" - latency: 1.819036ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T16:37:19Z" kind: List metadata: resourceVersion: ""